Skip to content

R
riscv-gcc-1
Commit a7bc3cdc by Jonathan Wakely
Options

index.txt: Regenerate after adding <link> tags. 

2003-12-12  Jonathan Wakely  <redi@gcc.gnu.org>

	* docs/html/faq/index.txt: Regenerate after adding <link> tags.

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