5. [25]_XOPEN_SOURCE / _GNU_SOURCE / etc is always defined
6. [26]OS X ctype.h is broken! How can I hack it?
7. [27]Threading is broken on i386
- 4. [28]Known Bugs and Non-Bugs
- 1. [29]What works already?
- 2. [30]Bugs in gcc/g++ (not libstdc++-v3)
- 3. [31]Bugs in the C++ language/lib specification
- 4. [32]Things in libstdc++ that only look like bugs
- o [33]reopening a stream fails
- o [34]-Weffc++ complains too much
- o [35]"ambiguous overloads" after including an old-style
+ 8. [28]Recent GNU/Linux glibc required?
+ 4. [29]Known Bugs and Non-Bugs
+ 1. [30]What works already?
+ 2. [31]Bugs in gcc/g++ (not libstdc++-v3)
+ 3. [32]Bugs in the C++ language/lib specification
+ 4. [33]Things in libstdc++ that only look like bugs
+ o [34]reopening a stream fails
+ o [35]-Weffc++ complains too much
+ o [36]"ambiguous overloads" after including an old-style
header
- o [36]The g++-3 headers are not ours
- o [37]compilation errors from streambuf.h
- o [38]errors about *Concept and constraints in the STL...
- o [39]program crashes when using library code in a
+ o [37]The g++-3 headers are not ours
+ o [38]compilation errors from streambuf.h
+ o [39]errors about *Concept and constraints in the STL...
+ o [40]program crashes when using library code in a
dynamically-loaded library
- 5. [40]Aw, that's easy to fix!
- 5. [41]Miscellaneous
- 1. [42]string::iterator is not char*; vector<T>::iterator is not
+ 5. [41]Aw, that's easy to fix!
+ 5. [42]Miscellaneous
+ 1. [43]string::iterator is not char*; vector<T>::iterator is not
T*
- 2. [43]What's next after libstdc++-v3?
- 3. [44]What about the STL from SGI?
- 4. [45]Extensions and Backward Compatibility
- 5. [46][removed]
- 6. [47]Is libstdc++-v3 thread-safe?
- 7. [48]How do I get a copy of the ISO C++ Standard?
- 8. [49]What's an ABI and why is it so messy?
+ 2. [44]What's next after libstdc++-v3?
+ 3. [45]What about the STL from SGI?
+ 4. [46]Extensions and Backward Compatibility
+ 5. [47][removed]
+ 6. [48]Is libstdc++-v3 thread-safe?
+ 7. [49]How do I get a copy of the ISO C++ Standard?
+ 8. [50]What's an ABI and why is it so messy?
_________________________________________________________________
1.0 General Information
The GNU Standard C++ Library v3 is an ongoing project to implement the
ISO 14882 Standard C++ library as described in chapters 17 through 27
and annex D. As the library reaches stable plateaus, it is captured in
- a snapshot and released. The latest release is [50]the fourteenth
+ a snapshot and released. The latest release is [51]the fourteenth
snapshot but newer versions have been included in recent GCC releases.
For those who want to see exactly how far the project has come, or
just want the latest bleeding-edge code, the up-to-date source is
available over anonymous CVS, and can even be browsed over the Web
- (see [51]1.4 below).
+ (see [52]1.4 below).
The older libstdc++-v2 project is no longer maintained; the code has
- been completely replaced and rewritten. [52]If you are using V2, then
+ been completely replaced and rewritten. [53]If you are using V2, then
you need to report bugs to your system vendor, not to the V3 list.
A more formal description of the V3 goals can be found in the official
- [53]design document.
+ [54]design document.
_________________________________________________________________
1.2 Why should I use libstdc++?
The GNU C/C++/FORTRAN/<pick-a-language> compiler (gcc, g++, etc) is
widely considered to be one of the leading compilers in the world. Its
- development has recently been taken over by the [54]GCC team. All of
- the rapid development and near-legendary [55]portability that are the
+ development has recently been taken over by the [55]GCC team. All of
+ the rapid development and near-legendary [56]portability that are the
hallmarks of an open-source project are being applied to libstdc++.
That means that all of the Standard classes and functions (such as
Development and discussion is held on the libstdc++ mailing list.
Subscribing to the list, or searching the list archives, is open to
- everyone. You can read instructions for doing so on the [56]homepage.
+ everyone. You can read instructions for doing so on the [57]homepage.
If you have questions, ideas, code, or are just curious, sign up!
_________________________________________________________________
1.4 How do I get libstdc++?
- The fourteenth (and latest) snapshot of libstdc++-v3 is [57]available
+ The fourteenth (and latest) snapshot of libstdc++-v3 is [58]available
via ftp.
- The [58]homepage has instructions for retrieving the latest CVS
+ The [59]homepage has instructions for retrieving the latest CVS
sources, and for browsing the CVS sources over the web.
The subset commonly known as the Standard Template Library (chapters
1.6 How do I contribute to the effort?
- Here is [59]a page devoted to this topic. Subscribing to the mailing
+ Here is [60]a page devoted to this topic. Subscribing to the mailing
list (see above, or the homepage) is a very good idea if you have
something to contribute, or if you have spare time and want to help.
Contributions don't have to be in the form of source code; anybody who
extracted into an updated utilities library, but nobody has stated
such a project yet.
- (The [60]Boost site houses free C++ libraries that do varying things,
+ (The [61]Boost site houses free C++ libraries that do varying things,
and happened to be started by members of the Standards Committee.
Certain "useful stuff" classes will probably migrate there.)
- For the bold and/or desperate, the [61]GCC extensions page describes
+ For the bold and/or desperate, the [62]GCC extensions page describes
where to find the last libg++ source.
_________________________________________________________________
remains unanswered, then just ask the mailing list. At present, you do
not need to be subscribed to the list to send a message to it. More
information is available on the homepage (including how to browse the
- list archives); to send to the list, use [62]libstdc++@gcc.gnu.org.
+ list archives); to send to the list, use [63]libstdc++@gcc.gnu.org.
If you have a question that you think should be included here, or if
- you have a question about a question/answer here, contact [63]Phil
- Edwards or [64]Gabriel Dos Reis.
+ you have a question about a question/answer here, contact [64]Phil
+ Edwards or [65]Gabriel Dos Reis.
_________________________________________________________________
1.9 What are the license terms for libstdc++-v3?
- See [65]our license description for these and related questions.
+ See [66]our license description for these and related questions.
_________________________________________________________________
2.0 Installation
* The GNU Autotools are needed if you are messing with the configury
or makefiles.
- The file [66]documentation.html provides a good overview of the steps
+ The file [67]documentation.html provides a good overview of the steps
necessary to build, install, and use the library. Instructions for
configuring the library with new flags such as --enable-threads are
there also, as well as patches and instructions for working with GCC
2.95.
- The top-level install.html and [67]RELEASE-NOTES files contain the
+ The top-level install.html and [68]RELEASE-NOTES files contain the
exact build and installation instructions. You may wish to browse
those files over CVSweb ahead of time to get a feel for what's
required. RELEASE-NOTES is located in the ".../docs/17_intro/"
The Concurrent Versions System is one of several revision control
packages. It was selected for GNU projects because it's free (speech),
- free (beer), and very high quality. The [68]CVS entry in the GNU
- software catalogue has a better description as well as a [69]link to
+ free (beer), and very high quality. The [69]CVS entry in the GNU
+ software catalogue has a better description as well as a [70]link to
the makers of CVS.
The "anonymous client checkout" feature of CVS is similar to anonymous
people don't like it, so here are two pseudo-solutions:
If the only functions from libstdc++.a which you need are language
- support functions (those listed in [70]clause 18 of the standard,
+ support functions (those listed in [71]clause 18 of the standard,
e.g., new and delete), then try linking against libsupc++.a (usually
specifying -lsupc++ when calling g++ for the final link step will do
it). This library contains only those support routines, one per object
- < /dev/null" to display a list of predefined macros for any
particular installation.
- This has been discussed on the mailing lists [71]quite a bit.
+ This has been discussed on the mailing lists [72]quite a bit.
This method is something of a wart. We'd like to find a cleaner
solution, but nobody yet has contributed the time.
3.6 OS X ctype.h is broken! How can I hack it?
This is a long-standing bug in the OS X support. Fortunately, the
- patch is quite simple, and well-known. [72]Here's a link to the
+ patch is quite simple, and well-known. [73]Here's a link to the
solution.
_________________________________________________________________
For 3.0.1, the most common "bug" is an apparently missing "../" in
include/Makefile, resulting in files like gthr.h and gthr-single.h not
- being found. Please read [73]the configuration instructions for GCC,
+ being found. Please read [74]the configuration instructions for GCC,
specifically the part about configuring in a separate build directory,
and how strongly recommended it is. Building in the source directory
is fragile, is rarely tested, and tends to break, as in this case.
For 3.1, the most common "bug" is a parse error when using <fstream>,
ending with a message, "bits/basic_file.h:52: parse error before `{'
- token." Please read [74]the installation instructions for GCC,
+ token." Please read [75]the installation instructions for GCC,
specifically the part about not installing newer versions on top of
older versions. If you install 3.1 over a 3.0.x release, then the
wrong basic_file.h header will be found (its location changed between
libstdc++. If you are experiencing one of these problems, you can find
more information on the libstdc++ and the GCC mailing lists.
- Before reporting a bug, examine the [75]bugs database with the
+ Before reporting a bug, examine the [76]bugs database with the
category set to "libstdc++". The BUGS file in the source tree also
tracks known serious problems.
* Debugging is problematic, due to bugs in line-number generation
(mostly fixed in the compiler) and gdb lagging behind the compiler
(lack of personnel). We recommend configuring the compiler using
--with-dwarf2 if the DWARF2 debugging format is not already the
- default on your platform. Also, [76]changing your GDB settings can
+ default on your platform. Also, [77]changing your GDB settings can
have a profound effect on your C++ debugging experiences. :-)
_________________________________________________________________
4.3 Bugs in the C++ language/lib specification
- Yes, unfortunately, there are some. In a [77]message to the list,
+ Yes, unfortunately, there are some. In a [78]message to the list,
Nathan Myers announced that he has started a list of problems in the
ISO C++ Standard itself, especially with regard to the chapters that
- concern the library. The list itself is [78]posted on his website.
+ concern the library. The list itself is [79]posted on his website.
Developers who are having problems interpreting the Standard may wish
to consult his notes.
For those people who are not part of the ISO Library Group (i.e.,
nearly all of us needing to read this page in the first place :-), a
- public list of the library defects is occasionally published [79]here.
- Some of these have resulted in [80]code changes.
+ public list of the library defects is occasionally published [80]here.
+ Some of these have resulted in [81]code changes.
_________________________________________________________________
4.4 Things in libstdc++ that only look like bugs
state on the previous file. The reason is that the state flags are not
cleared on a successful call to open(). The standard unfortunately did
not specify behavior in this case, and to everybody's great sorrow,
- the [81]proposed LWG resolution (see DR #22) is to leave the flags
+ the [82]proposed LWG resolution (see DR #22) is to leave the flags
unchanged. You must insert a call to fs.clear() between the calls to
close() and open(), and then everything will work like we all expect
it to work.
same namespace as other comparison functions (e.g., 'using' them and
the <iterator> header), then you will suddenly be faced with huge
numbers of ambiguity errors. This was discussed on the -v3 list;
- Nathan Myers [82]sums things up here. The collisions with
+ Nathan Myers [83]sums things up here. The collisions with
vector/string iterator types have been fixed for 3.1.
The g++-3 headers are not ours
If you have found an extremely broken header file which is causing
problems for you, look carefully before submitting a "high" priority
bug report (which you probably shouldn't do anyhow; see the last
- paragraph of the page describing [83]the GCC bug database).
+ paragraph of the page describing [84]the GCC bug database).
If the headers are in ${prefix}/include/g++-3, or if the installed
library's name looks like libstdc++-2.10.a or libstdc++-libc6-2.10.so,
Currently our header files are installed in ${prefix}/include/g++-v3
(see the 'v'?). This may change with the next release of GCC, as it
- may be too confusing, but [84]the question has not yet been decided.
+ may be too confusing, but [85]the question has not yet been decided.
glibc If you're on a GNU/Linux system and have just upgraded to glibc
2.2, but are still using gcc 2.95.2, then you should have read the
http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
- Note that 2.95.x shipped with the [85]old v2 library which is no
+ Note that 2.95.x shipped with the [86]old v2 library which is no
longer maintained. Also note that gcc 2.95.3 fixes this problem, but
requires a separate patch for libstdc++-v3.
visibility, or you just plain forgot, etc).
More information, including how to optionally enable/disable the
- checks, is available [86]here.
+ checks, is available [87]here.
dlopen/dlsym If you are using the C++ library across
dynamically-loaded objects, make certain that you are passing the
If you have found a bug in the library and you think you have a
working fix, then send it in! The main GCC site has a page on
- [87]submitting patches that covers the procedure, but for libstdc++
+ [88]submitting patches that covers the procedure, but for libstdc++
you should also send the patch to our mailing list in addition to the
- GCC patches mailing list. The libstdc++ [88]contributors' page also
+ GCC patches mailing list. The libstdc++ [89]contributors' page also
talks about how to submit patches.
In addition to the description, the patch, and the ChangeLog entry, it
is a Good Thing if you can additionally create a small test program to
test for the presence of the bug that your patch fixes. Bugs have a
way of being reintroduced; if an old bug creeps back in, it will be
- caught immediately by the [89]testsuite -- but only if such a test
+ caught immediately by the [90]testsuite -- but only if such a test
exists.
_________________________________________________________________
libstdc++. Some of that is already happening, see 4.2. Some of
those changes are being predicted by the library maintainers, and
we add code to the library based on what the current proposed
- resolution specifies. Those additions are listed in [90]the
+ resolution specifies. Those additions are listed in [91]the
extensions page.
2. Performance tuning. Lots of performance tuning. This too is
already underway for post-3.0 releases, starting with memory
type from C99.) Bugfixes and rewrites (to improve or fix thread
safety, for instance) will of course be a continuing task.
- [91]This question about the next libstdc++ prompted some brief but
- interesting [92]speculation.
+ [92]This question about the next libstdc++ prompted some brief but
+ interesting [93]speculation.
_________________________________________________________________
5.3 What about the STL from SGI?
- The [93]STL from SGI, version 3.3, was the most recent merge of the
+ The [94]STL from SGI, version 3.3, was the most recent merge of the
STL codebase. The code in libstdc++ contains many fixes and changes,
and it is very likely that the SGI code is no longer under active
development. We expect that no future merges will take place.
This is a bit cleaner than defining typedefs for all the
instantiations you might need.
- Extensions to the library have [94]their own page.
+ Extensions to the library have [95]their own page.
_________________________________________________________________
5.5 [removed]
otherwise documented as safe, do not assume that two threads may
access a shared standard library object at the same time.
- See chapters [95]17 (library introduction), [96]23 (containers), and
- [97]27 (I/O) for more information.
+ See chapters [96]17 (library introduction), [97]23 (containers), and
+ [98]27 (I/O) for more information.
_________________________________________________________________
5.7 How do I get a copy of the ISO C++ Standard?
their two-meeting commitment for voting rights, may get a copy of the
standard from their respective national standards organization. In the
USA, this national standards organization is ANSI and their website is
- right [98]here. (And if you've already registered with them, clicking
- this link will take you to directly to the place where you can [99]buy
- the standard on-line.
+ right [99]here. (And if you've already registered with them, clicking
+ this link will take you to directly to the place where you can
+ [100]buy the standard on-line.
- Who is your country's member body? Visit the [100]ISO homepage and
+ Who is your country's member body? Visit the [101]ISO homepage and
find out!
_________________________________________________________________
encompasses the standard library.
_________________________________________________________________
- See [101]license.html for copying conditions. Comments and suggestions
- are welcome, and may be sent to [102]the libstdc++ mailing list.
+ See [102]license.html for copying conditions. Comments and suggestions
+ are welcome, and may be sent to [103]the libstdc++ mailing list.
References
25. ../faq/index.html#3_5
26. ../faq/index.html#3_6
27. ../faq/index.html#3_7
- 28. ../faq/index.html#4_0
- 29. ../faq/index.html#4_1
- 30. ../faq/index.html#4_2
- 31. ../faq/index.html#4_3
- 32. ../faq/index.html#4_4
- 33. ../faq/index.html#4_4_iostreamclear
- 34. ../faq/index.html#4_4_Weff
- 35. ../faq/index.html#4_4_rel_ops
- 36. ../faq/index.html#4_4_interface
- 37. ../faq/index.html#4_4_glibc
- 38. ../faq/index.html#4_4_checks
- 39. ../faq/index.html#4_4_dlsym
- 40. ../faq/index.html#4_5
- 41. ../faq/index.html#5_0
- 42. ../faq/index.html#5_1
- 43. ../faq/index.html#5_2
- 44. ../faq/index.html#5_3
- 45. ../faq/index.html#5_4
- 46. ../faq/index.html#5_5
- 47. ../faq/index.html#5_6
- 48. ../faq/index.html#5_7
- 49. ../faq/index.html#5_8
- 50. http://gcc.gnu.org/libstdc++/index.html#download
- 51. ../faq/index.html#1_4
- 52. ../faq/index.html#4_4_interface
- 53. ../17_intro/DESIGN
- 54. http://gcc.gnu.org/
- 55. http://gcc.gnu.org/gcc-3.0/buildstat.html
- 56. http://gcc.gnu.org/libstdc++/
- 57. http://gcc.gnu.org/libstdc++/index.html#download
- 58. http://gcc.gnu.org/libstdc++/
- 59. ../17_intro/contribute.html
- 60. http://www.boost.org/
- 61. http://gcc.gnu.org/extensions.html
- 62. mailto:libstdc++@gcc.gnu.org
- 63. mailto:pme@gcc.gnu.org
- 64. mailto:gdr@gcc.gnu.org
- 65. ../17_intro/license.html
- 66. ../documentation.html
- 67. ../17_intro/RELEASE-NOTES
- 68. http://www.gnu.org/software/cvs/cvs.html
- 69. http://www.cvshome.org/
- 70. ../18_support/howto.html
- 71. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
- 72. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
- 73. http://gcc.gnu.org/install/configure.html
- 74. http://gcc.gnu.org/install/
- 75. http://gcc.gnu.org/bugs.html
- 76. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
- 77. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
- 78. http://www.cantrip.org/draft-bugs.txt
- 79. http://anubis.dkuug.dk/jtc1/sc22/wg21/
- 80. ../faq/index.html#5_2
- 81. ../ext/howto.html#5
- 82. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
- 83. http://gcc.gnu.org/gnatswrite.html
- 84. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
- 85. ../faq/index.html#4_4_interface
- 86. ../19_diagnostics/howto.html#3
- 87. http://gcc.gnu.org/contribute.html
- 88. ../17_intro/contribute.html
- 89. ../faq/index.html#2_4
- 90. ../ext/howto.html#5
- 91. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
- 92. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
- 93. http://www.sgi.com/Technology/STL/
- 94. ../ext/howto.html
- 95. ../17_intro/howto.html#3
- 96. ../23_containers/howto.html#3
- 97. ../27_io/howto.html#9
- 98. http://www.ansi.org/
- 99. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
- 100. http://www.iso.ch/
- 101. ../17_intro/license.html
- 102. mailto:libstdc++@gcc.gnu.org
+ 28. ../faq/index.html#3_8
+ 29. ../faq/index.html#4_0
+ 30. ../faq/index.html#4_1
+ 31. ../faq/index.html#4_2
+ 32. ../faq/index.html#4_3
+ 33. ../faq/index.html#4_4
+ 34. ../faq/index.html#4_4_iostreamclear
+ 35. ../faq/index.html#4_4_Weff
+ 36. ../faq/index.html#4_4_rel_ops
+ 37. ../faq/index.html#4_4_interface
+ 38. ../faq/index.html#4_4_glibc
+ 39. ../faq/index.html#4_4_checks
+ 40. ../faq/index.html#4_4_dlsym
+ 41. ../faq/index.html#4_5
+ 42. ../faq/index.html#5_0
+ 43. ../faq/index.html#5_1
+ 44. ../faq/index.html#5_2
+ 45. ../faq/index.html#5_3
+ 46. ../faq/index.html#5_4
+ 47. ../faq/index.html#5_5
+ 48. ../faq/index.html#5_6
+ 49. ../faq/index.html#5_7
+ 50. ../faq/index.html#5_8
+ 51. http://gcc.gnu.org/libstdc++/index.html#download
+ 52. ../faq/index.html#1_4
+ 53. ../faq/index.html#4_4_interface
+ 54. ../17_intro/DESIGN
+ 55. http://gcc.gnu.org/
+ 56. http://gcc.gnu.org/gcc-3.0/buildstat.html
+ 57. http://gcc.gnu.org/libstdc++/
+ 58. http://gcc.gnu.org/libstdc++/index.html#download
+ 59. http://gcc.gnu.org/libstdc++/
+ 60. ../17_intro/contribute.html
+ 61. http://www.boost.org/
+ 62. http://gcc.gnu.org/extensions.html
+ 63. mailto:libstdc++@gcc.gnu.org
+ 64. mailto:pme@gcc.gnu.org
+ 65. mailto:gdr@gcc.gnu.org
+ 66. ../17_intro/license.html
+ 67. ../documentation.html
+ 68. ../17_intro/RELEASE-NOTES
+ 69. http://www.gnu.org/software/cvs/cvs.html
+ 70. http://www.cvshome.org/
+ 71. ../18_support/howto.html
+ 72. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
+ 73. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
+ 74. http://gcc.gnu.org/install/configure.html
+ 75. http://gcc.gnu.org/install/
+ 76. http://gcc.gnu.org/bugs.html
+ 77. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
+ 78. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
+ 79. http://www.cantrip.org/draft-bugs.txt
+ 80. http://anubis.dkuug.dk/jtc1/sc22/wg21/
+ 81. ../faq/index.html#5_2
+ 82. ../ext/howto.html#5
+ 83. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
+ 84. http://gcc.gnu.org/gnatswrite.html
+ 85. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
+ 86. ../faq/index.html#4_4_interface
+ 87. ../19_diagnostics/howto.html#3
+ 88. http://gcc.gnu.org/contribute.html
+ 89. ../17_intro/contribute.html
+ 90. ../faq/index.html#2_4
+ 91. ../ext/howto.html#5
+ 92. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
+ 93. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
+ 94. http://www.sgi.com/Technology/STL/
+ 95. ../ext/howto.html
+ 96. ../17_intro/howto.html#3
+ 97. ../23_containers/howto.html#3
+ 98. ../27_io/howto.html#9
+ 99. http://www.ansi.org/
+ 100. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
+ 101. http://www.iso.ch/
+ 102. ../17_intro/license.html
+ 103. mailto:libstdc++@gcc.gnu.org
OSDN Git Service
