Skip to content

R
riscv-gcc-1
Commit fa587f4c by Phil Edwards
Options

index.html (3.10): Add note about mips atomicity.h. 

2003-05-06  Phil Edwards  <pme@gcc.gnu.org>

	* docs/html/faq/index.html (3.10):  Add note about mips atomicity.h.
	* docs/html/faq/index.txt:  Regenerated.

From-SVN: r66536
parent aa1a100b
Showing with 186 additions and 156 deletions
libstdc++-v3/ChangeLog
2003-05-06 Phil Edwards <pme@gcc.gnu.org>
* docs/html/faq/index.html (3.10): Add note about mips atomicity.h.
* docs/html/faq/index.txt: Regenerated.
2003-05-06 Michael Ritzert <Ritzert@t-online.de> 2003-05-06 Michael Ritzert <Ritzert@t-online.de>
Matt Kraai <kraai@alumni.cmu.edu> Matt Kraai <kraai@alumni.cmu.edu>
......
libstdc++-v3/docs/html/faq/index.html
...@@ -76,6 +76,7 @@ ...@@ -76,6 +76,7 @@
<li><a href="#3_7">Threading is broken on i386</a></li> <li><a href="#3_7">Threading is broken on i386</a></li>
<li><a href="#3_8">Recent GNU/Linux glibc required?</a></li> <li><a href="#3_8">Recent GNU/Linux glibc required?</a></li>
<li><a href="#3_9">Can't use wchar_t/wstring on FreeBSD</a></li> <li><a href="#3_9">Can't use wchar_t/wstring on FreeBSD</a></li>
<li><a href="#3_10">MIPS atomic operations</a></li>
</ol> </ol>
</li> </li>
...@@ -544,6 +545,17 @@ which is no longer available, thanks deja...--> ...@@ -544,6 +545,17 @@ which is no longer available, thanks deja...-->
</p> </p>
<hr /> <hr />
<h2><a name="3_10">3.10 MIPS atomic operations</a></h2>
<p>The atomic locking routines for MIPS targets requires MIPS II
and later. A patch went in just after the 3.3.0 release to
make mips* use the generic implementation instead. You can also
configure for mipsel-elf as a workaround.
</p>
<p>mips*-*-linux* continues to use the MIPS II routines, and more
work in this area is expected.
</p>
<hr />
<h1><a name="4_0">4.0 Known Bugs and Non-Bugs</a></h1> <h1><a name="4_0">4.0 Known Bugs and Non-Bugs</a></h1>
<em>Note that this section can get rapdily outdated -- such is the <em>Note that this section can get rapdily outdated -- such is the
nature of an open-source project. For the latest information, join nature of an open-source project. For the latest information, join
......
libstdc++-v3/docs/html/faq/index.txt
...@@ -37,32 +37,33 @@ ...@@ -37,32 +37,33 @@
7. [27]Threading is broken on i386 7. [27]Threading is broken on i386
8. [28]Recent GNU/Linux glibc required? 8. [28]Recent GNU/Linux glibc required?
9. [29]Can't use wchar_t/wstring on FreeBSD 9. [29]Can't use wchar_t/wstring on FreeBSD
4. [30]Known Bugs and Non-Bugs 10. [30]MIPS atomic operations
1. [31]What works already? 4. [31]Known Bugs and Non-Bugs
2. [32]Bugs in gcc/g++ (not libstdc++-v3) 1. [32]What works already?
3. [33]Bugs in the C++ language/lib specification 2. [33]Bugs in gcc/g++ (not libstdc++-v3)
4. [34]Things in libstdc++ that only look like bugs 3. [34]Bugs in the C++ language/lib specification
o [35]reopening a stream fails 4. [35]Things in libstdc++ that only look like bugs
o [36]-Weffc++ complains too much o [36]reopening a stream fails
o [37]"ambiguous overloads" after including an old-style o [37]-Weffc++ complains too much
o [38]"ambiguous overloads" after including an old-style
header header
o [38]The g++-3 headers are not ours o [39]The g++-3 headers are not ours
o [39]compilation errors from streambuf.h o [40]compilation errors from streambuf.h
o [40]errors about *Concept and constraints in the STL... o [41]errors about *Concept and constraints in the STL...
o [41]program crashes when using library code in a o [42]program crashes when using library code in a
dynamically-loaded library dynamically-loaded library
o [42]"memory leaks" in containers o [43]"memory leaks" in containers
5. [43]Aw, that's easy to fix! 5. [44]Aw, that's easy to fix!
5. [44]Miscellaneous 5. [45]Miscellaneous
1. [45]string::iterator is not char*; vector<T>::iterator is not 1. [46]string::iterator is not char*; vector<T>::iterator is not
T* T*
2. [46]What's next after libstdc++-v3? 2. [47]What's next after libstdc++-v3?
3. [47]What about the STL from SGI? 3. [48]What about the STL from SGI?
4. [48]Extensions and Backward Compatibility 4. [49]Extensions and Backward Compatibility
5. [49][removed] 5. [50][removed]
6. [50]Is libstdc++-v3 thread-safe? 6. [51]Is libstdc++-v3 thread-safe?
7. [51]How do I get a copy of the ISO C++ Standard? 7. [52]How do I get a copy of the ISO C++ Standard?
8. [52]What's an ABI and why is it so messy? 8. [53]What's an ABI and why is it so messy?
_________________________________________________________________ _________________________________________________________________
1.0 General Information 1.0 General Information
...@@ -72,19 +73,19 @@ ...@@ -72,19 +73,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 [53]the fourteenth a snapshot and released. The latest release is [54]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 [54]1.4 below). (see [55]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. [55]If you are using V2, then been completely replaced and rewritten. [56]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
[56]design document. [57]design document.
_________________________________________________________________ _________________________________________________________________
1.2 Why should I use libstdc++? 1.2 Why should I use libstdc++?
...@@ -97,8 +98,8 @@ ...@@ -97,8 +98,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 [57]GCC team. All of development has recently been taken over by the [58]GCC team. All of
the rapid development and near-legendary [58]portability that are the the rapid development and near-legendary [59]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
...@@ -116,16 +117,16 @@ ...@@ -116,16 +117,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 [59]homepage. everyone. You can read instructions for doing so on the [60]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 [60]homepage has instructions for retrieving the latest CVS The [61]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 [61]the Stable versions of libstdc++-v3 are included with releases of [62]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
...@@ -141,7 +142,7 @@ ...@@ -141,7 +142,7 @@
1.6 How do I contribute to the effort? 1.6 How do I contribute to the effort?
Here is [62]a page devoted to this topic. Subscribing to the mailing Here is [63]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
...@@ -176,11 +177,11 @@ ...@@ -176,11 +177,11 @@
extracted into an updated utilities library, but nobody has stated extracted into an updated utilities library, but nobody has stated
such a project yet. such a project yet.
(The [63]Boost site houses free C++ libraries that do varying things, (The [64]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 [64]GCC extensions page describes For the bold and/or desperate, the [65]GCC extensions page describes
where to find the last libg++ source. where to find the last libg++ source.
_________________________________________________________________ _________________________________________________________________
...@@ -190,16 +191,16 @@ ...@@ -190,16 +191,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 [65]libstdc++@gcc.gnu.org. list archives); to send to the list, use [66]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 [66]Phil you have a question about a question/answer here, contact [67]Phil
Edwards or [67]Gabriel Dos Reis. Edwards or [68]Gabriel Dos Reis.
_________________________________________________________________ _________________________________________________________________
1.9 What are the license terms for libstdc++-v3? 1.9 What are the license terms for libstdc++-v3?
See [68]our license description for these and related questions. See [69]our license description for these and related questions.
_________________________________________________________________ _________________________________________________________________
2.0 Installation 2.0 Installation
...@@ -216,13 +217,13 @@ ...@@ -216,13 +217,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 [69]documentation.html provides a good overview of the steps The file [70]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 [70]RELEASE-NOTES files contain the The top-level install.html and [71]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/"
...@@ -239,8 +240,8 @@ ...@@ -239,8 +240,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 [71]CVS entry in the GNU free (beer), and very high quality. The [72]CVS entry in the GNU
software catalogue has a better description as well as a [72]link to software catalogue has a better description as well as a [73]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
...@@ -254,7 +255,7 @@ ...@@ -254,7 +255,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 [73]here. need DejaGNU, as described [74]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
...@@ -292,7 +293,7 @@ ...@@ -292,7 +293,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 [74]clause 18 of the standard, support functions (those listed in [75]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
...@@ -387,7 +388,7 @@ ...@@ -387,7 +388,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 [75]quite a bit. This has been discussed on the mailing lists [76]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.
...@@ -396,7 +397,7 @@ ...@@ -396,7 +397,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. [76]Here's a link to the patch is quite simple, and well-known. [77]Here's a link to the
solution. solution.
_________________________________________________________________ _________________________________________________________________
...@@ -434,10 +435,21 @@ ...@@ -434,10 +435,21 @@
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 [77]this short thread ("_GLIBCPP_USE_WCHAR_T undefined in by reading [78]this short thread ("_GLIBCPP_USE_WCHAR_T undefined in
FreeBSD's c++config.h?"). FreeBSD's c++config.h?").
_________________________________________________________________ _________________________________________________________________
3.10 MIPS atomic operations
The atomic locking routines for MIPS targets requires MIPS II and
later. A patch went in just after the 3.3.0 release to make mips* use
the generic implementation instead. You can also configure for
mipsel-elf as a workaround.
mips*-*-linux* continues to use the MIPS II routines, and more work in
this area is expected.
_________________________________________________________________
4.0 Known Bugs and Non-Bugs 4.0 Known Bugs and Non-Bugs
Note that this section can get rapdily outdated -- such is the nature Note that this section can get rapdily outdated -- such is the nature
...@@ -447,7 +459,7 @@ ...@@ -447,7 +459,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 [78]the configuration instructions for GCC, being found. Please read [79]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.
...@@ -455,7 +467,7 @@ ...@@ -455,7 +467,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 [79]the installation instructions for GCC, token." Please read [80]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
...@@ -488,30 +500,30 @@ New: ...@@ -488,30 +500,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 [80]bugs database with the Before reporting a bug, examine the [81]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, [81]changing your GDB settings can default on your platform. Also, [82]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 [82]message to the list, Yes, unfortunately, there are some. In a [83]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 [83]posted on his website. concern the library. The list itself is [84]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 [84]here. public list of the library defects is occasionally published [85]here.
Some of these have resulted in [85]code changes. Some of these have resulted in [86]code changes.
_________________________________________________________________ _________________________________________________________________
4.4 Things in libstdc++ that only look like bugs 4.4 Things in libstdc++ that only look like bugs
...@@ -543,7 +555,7 @@ New: ...@@ -543,7 +555,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 [86]proposed LWG resolution in DR #22 is to leave the flags the [87]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.
...@@ -553,7 +565,7 @@ New: ...@@ -553,7 +565,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 [87]sums things up here. The collisions with Nathan Myers [88]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
...@@ -561,7 +573,7 @@ New: ...@@ -561,7 +573,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 [88]the GCC bug database). paragraph of the page describing [89]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,
...@@ -586,7 +598,7 @@ type has changed in glibc 2.2. The patch is at ...@@ -586,7 +598,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 [89]old v2 library which is no Note that 2.95.x shipped with the [90]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.
...@@ -599,7 +611,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -599,7 +611,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 [90]here. checks, is available [91]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
...@@ -618,11 +630,11 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -618,11 +630,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 [91]valgrind. The library's default allocators keep checkers such as [92]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 [92]Tips for want to test the library for memory leaks please read [93]Tips for
memory leak hunting first. memory leak hunting first.
_________________________________________________________________ _________________________________________________________________
...@@ -630,16 +642,16 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -630,16 +642,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
[93]submitting patches that covers the procedure, but for libstdc++ [94]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++ [94]contributors' page also GCC patches mailing list. The libstdc++ [95]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 [95]testsuite -- but only if such a test caught immediately by the [96]testsuite -- but only if such a test
exists. exists.
_________________________________________________________________ _________________________________________________________________
...@@ -673,7 +685,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -673,7 +685,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 [96]the resolution specifies. Those additions are listed in [97]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
...@@ -689,13 +701,13 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -689,13 +701,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.
[97]This question about the next libstdc++ prompted some brief but [98]This question about the next libstdc++ prompted some brief but
interesting [98]speculation. interesting [99]speculation.
_________________________________________________________________ _________________________________________________________________
5.3 What about the STL from SGI? 5.3 What about the STL from SGI?
The [99]STL from SGI, version 3.3, was the most recent merge of the The [100]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.
...@@ -745,7 +757,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -745,7 +757,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
This is a bit cleaner than defining typedefs for all the This is a bit cleaner than defining typedefs for all the
instantiations you might need. instantiations you might need.
Extensions to the library have [100]their own page. Extensions to the library have [101]their own page.
_________________________________________________________________ _________________________________________________________________
5.5 [removed] 5.5 [removed]
...@@ -798,8 +810,8 @@ a ...@@ -798,8 +810,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 [101]17 (library introduction), [102]23 (containers), and See chapters [102]17 (library introduction), [103]23 (containers), and
[103]27 (I/O) for more information. [104]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?
...@@ -810,11 +822,11 @@ a ...@@ -810,11 +822,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 [104]here. (And if you've already registered with them, clicking right [105]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
[105]buy the standard on-line. [106]buy the standard on-line.
Who is your country's member body? Visit the [106]ISO homepage and Who is your country's member body? Visit the [107]ISO homepage and
find out! find out!
_________________________________________________________________ _________________________________________________________________
...@@ -865,8 +877,8 @@ a ...@@ -865,8 +877,8 @@ a
encompasses the standard library. encompasses the standard library.
_________________________________________________________________ _________________________________________________________________
See [107]license.html for copying conditions. Comments and suggestions See [108]license.html for copying conditions. Comments and suggestions
are welcome, and may be sent to [108]the libstdc++ mailing list. are welcome, and may be sent to [109]the libstdc++ mailing list.
References References
...@@ -899,82 +911,83 @@ References ...@@ -899,82 +911,83 @@ References
27. ../faq/index.html#3_7 27. ../faq/index.html#3_7
28. ../faq/index.html#3_8 28. ../faq/index.html#3_8
29. ../faq/index.html#3_9 29. ../faq/index.html#3_9
30. ../faq/index.html#4_0 30. ../faq/index.html#3_10
31. ../faq/index.html#4_1 31. ../faq/index.html#4_0
32. ../faq/index.html#4_2 32. ../faq/index.html#4_1
33. ../faq/index.html#4_3 33. ../faq/index.html#4_2
34. ../faq/index.html#4_4 34. ../faq/index.html#4_3
35. ../faq/index.html#4_4_iostreamclear 35. ../faq/index.html#4_4
36. ../faq/index.html#4_4_Weff 36. ../faq/index.html#4_4_iostreamclear
37. ../faq/index.html#4_4_rel_ops 37. ../faq/index.html#4_4_Weff
38. ../faq/index.html#4_4_interface 38. ../faq/index.html#4_4_rel_ops
39. ../faq/index.html#4_4_glibc 39. ../faq/index.html#4_4_interface
40. ../faq/index.html#4_4_checks 40. ../faq/index.html#4_4_glibc
41. ../faq/index.html#4_4_dlsym 41. ../faq/index.html#4_4_checks
42. ../faq/index.html#4_4_leak 42. ../faq/index.html#4_4_dlsym
43. ../faq/index.html#4_5 43. ../faq/index.html#4_4_leak
44. ../faq/index.html#5_0 44. ../faq/index.html#4_5
45. ../faq/index.html#5_1 45. ../faq/index.html#5_0
46. ../faq/index.html#5_2 46. ../faq/index.html#5_1
47. ../faq/index.html#5_3 47. ../faq/index.html#5_2
48. ../faq/index.html#5_4 48. ../faq/index.html#5_3
49. ../faq/index.html#5_5 49. ../faq/index.html#5_4
50. ../faq/index.html#5_6 50. ../faq/index.html#5_5
51. ../faq/index.html#5_7 51. ../faq/index.html#5_6
52. ../faq/index.html#5_8 52. ../faq/index.html#5_7
53. http://gcc.gnu.org/libstdc++/index.html#download 53. ../faq/index.html#5_8
54. ../faq/index.html#1_4 54. http://gcc.gnu.org/libstdc++/index.html#download
55. ../faq/index.html#4_4_interface 55. ../faq/index.html#1_4
56. ../17_intro/DESIGN 56. ../faq/index.html#4_4_interface
57. http://gcc.gnu.org/ 57. ../17_intro/DESIGN
58. http://gcc.gnu.org/gcc-3.0/buildstat.html 58. http://gcc.gnu.org/
59. http://gcc.gnu.org/libstdc++/ 59. http://gcc.gnu.org/gcc-3.0/buildstat.html
60. http://gcc.gnu.org/libstdc++/ 60. http://gcc.gnu.org/libstdc++/
61. http://gcc.gnu.org/releases.html 61. http://gcc.gnu.org/libstdc++/
62. ../17_intro/contribute.html 62. http://gcc.gnu.org/releases.html
63. http://www.boost.org/ 63. ../17_intro/contribute.html
64. http://gcc.gnu.org/extensions.html 64. http://www.boost.org/
65. mailto:libstdc++@gcc.gnu.org 65. http://gcc.gnu.org/extensions.html
66. mailto:pme@gcc.gnu.org 66. mailto:libstdc++@gcc.gnu.org
67. mailto:gdr@gcc.gnu.org 67. mailto:pme@gcc.gnu.org
68. ../17_intro/license.html 68. mailto:gdr@gcc.gnu.org
69. ../documentation.html 69. ../17_intro/license.html
70. ../17_intro/RELEASE-NOTES 70. ../documentation.html
71. http://www.gnu.org/software/cvs/cvs.html 71. ../17_intro/RELEASE-NOTES
72. http://www.cvshome.org/ 72. http://www.gnu.org/software/cvs/cvs.html
73. http://gcc.gnu.org/install/test.html 73. http://www.cvshome.org/
74. ../18_support/howto.html 74. http://gcc.gnu.org/install/test.html
75. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris 75. ../18_support/howto.html
76. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html 76. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
77. http://gcc.gnu.org/ml/libstdc++/2003-02/subjects.html#00286 77. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
78. http://gcc.gnu.org/install/configure.html 78. http://gcc.gnu.org/ml/libstdc++/2003-02/subjects.html#00286
79. http://gcc.gnu.org/install/ 79. http://gcc.gnu.org/install/configure.html
80. http://gcc.gnu.org/bugs.html 80. http://gcc.gnu.org/install/
81. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html 81. http://gcc.gnu.org/bugs.html
82. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html 82. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
83. http://www.cantrip.org/draft-bugs.txt 83. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
84. http://anubis.dkuug.dk/jtc1/sc22/wg21/ 84. http://www.cantrip.org/draft-bugs.txt
85. ../faq/index.html#5_2 85. http://anubis.dkuug.dk/jtc1/sc22/wg21/
86. ../ext/howto.html#5 86. ../faq/index.html#5_2
87. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html 87. ../ext/howto.html#5
88. http://gcc.gnu.org/gnatswrite.html 88. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
89. ../faq/index.html#4_4_interface 89. http://gcc.gnu.org/gnatswrite.html
90. ../19_diagnostics/howto.html#3 90. ../faq/index.html#4_4_interface
91. http://developer.kde.org/~sewardj/ 91. ../19_diagnostics/howto.html#3
92. ../debug.html#mem 92. http://developer.kde.org/~sewardj/
93. http://gcc.gnu.org/contribute.html 93. ../debug.html#mem
94. ../17_intro/contribute.html 94. http://gcc.gnu.org/contribute.html
95. ../faq/index.html#2_4 95. ../17_intro/contribute.html
96. ../ext/howto.html#5 96. ../faq/index.html#2_4
97. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html 97. ../ext/howto.html#5
98. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html 98. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
99. http://www.sgi.com/Technology/STL/ 99. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
100. ../ext/howto.html 100. http://www.sgi.com/Technology/STL/
101. ../17_intro/howto.html#3 101. ../ext/howto.html
102. ../23_containers/howto.html#3 102. ../17_intro/howto.html#3
103. ../27_io/howto.html#9 103. ../23_containers/howto.html#3
104. http://www.ansi.org/ 104. ../27_io/howto.html#9
105. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 105. http://www.ansi.org/
106. http://www.iso.ch/ 106. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
107. ../17_intro/license.html 107. http://www.iso.ch/
108. mailto:libstdc++@gcc.gnu.org 108. ../17_intro/license.html
109. 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