Skip to content

R
riscv-gcc-1
Commit d815ea49 by Phil Edwards Committed by Phil Edwards
Options

index.html: Update version references. 

2004-07-29  Phil Edwards  <phil@codesourcery.com>

	* docs/html/faq/index.html:  Update version references.  Make
	clear that code from SGI has diverged greatly.  Remove references
	to library snapshots and what's-new sections.
	* docs/html/faq/index.txt:  Regenerate.

From-SVN: r85289
parent 91683ccd
Showing with 270 additions and 287 deletions
libstdc++-v3/ChangeLog
2004-07-29 Phil Edwards <phil@codesourcery.com>
* docs/html/faq/index.html: Update version references. Make
clear that code from SGI has diverged greatly. Remove references
to library snapshots and what's-new sections.
* docs/html/faq/index.txt: Regenerate.
2004-07-28 Matt Austern <austern@apple.com> 2004-07-28 Matt Austern <austern@apple.com>
* include/bits/stl_construct.h (_Destroy): New three-argument * include/bits/stl_construct.h (_Destroy): New three-argument
......
libstdc++-v3/docs/html/faq/index.html
...@@ -13,10 +13,6 @@ ...@@ -13,10 +13,6 @@
<link rel="Start" rev="Help" href="../documentation.html" type="text/html" <link rel="Start" rev="Help" href="../documentation.html" type="text/html"
title="GNU C++ Standard Library" /> title="GNU C++ Standard Library" />
<link rel="Copyright" href="../17_intro/license.html" type="text/html" /> <link rel="Copyright" href="../17_intro/license.html" type="text/html" />
<!--
** Locations of "the most recent snapshot is the Nth" text are
** answers 1_1, .
-->
</head> </head>
<body> <body>
...@@ -137,12 +133,8 @@ ...@@ -137,12 +133,8 @@
<h2><a name="1_1">1.1 What is libstdc++-v3?</a></h2> <h2><a name="1_1">1.1 What is libstdc++-v3?</a></h2>
<p>The GNU Standard C++ Library v3 is an <p>The GNU Standard C++ Library v3 is an
ongoing project to implement the ISO 14882 Standard C++ library ongoing project to implement the ISO 14882 Standard C++ library
as described in chapters 17 through 27 and annex D. As the as described in chapters 17 through 27 and annex D.
library reaches stable plateaus, it is captured in a snapshot For those who want to see exactly how
and released. The latest release is
<a href="http://gcc.gnu.org/libstdc++/index.html#download">the
fourteenth snapshot</a> 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 far the project has come, or just want the latest
bleeding-edge code, the up-to-date source is available over bleeding-edge code, the up-to-date source is available over
anonymous CVS, and can even be browsed over the Web (see anonymous CVS, and can even be browsed over the Web (see
...@@ -169,10 +161,10 @@ ...@@ -169,10 +161,10 @@
<p>The GNU C/C++/FORTRAN/&lt;pick-a-language&gt; compiler <p>The GNU C/C++/FORTRAN/&lt;pick-a-language&gt; compiler
(<code>gcc</code>, <code>g++</code>, etc) is widely considered to be (<code>gcc</code>, <code>g++</code>, etc) is widely considered to be
one of the leading compilers in the world. Its development one of the leading compilers in the world. Its development
has recently been taken over by the is overseen by the
<a href="http://gcc.gnu.org/">GCC team</a>. All of <a href="http://gcc.gnu.org/">GCC team</a>. All of
the rapid development and near-legendary the rapid development and near-legendary
<a href="http://gcc.gnu.org/gcc-3.0/buildstat.html">portability</a> <a href="http://gcc.gnu.org/gcc-3.3/buildstat.html">portability</a>
that are the hallmarks of an open-source project are being that are the hallmarks of an open-source project are being
applied to libstdc++. applied to libstdc++.
</p> </p>
...@@ -209,7 +201,7 @@ ...@@ -209,7 +201,7 @@
</p> </p>
<p>The subset commonly known as the Standard Template Library <p>The subset commonly known as the Standard Template Library
(chapters 23 through 25, mostly) is adapted from the final release (chapters 23 through 25, mostly) is adapted from the final release
of the SGI STL. of the SGI STL, with extensive changes.
</p> </p>
<hr /> <hr />
...@@ -306,7 +298,7 @@ which is no longer available, thanks deja...--> ...@@ -306,7 +298,7 @@ which is no longer available, thanks deja...-->
series was. If you are using GCC 2.95, you can still series was. If you are using GCC 2.95, you can still
build earlier snapshots of libstdc++. build earlier snapshots of libstdc++.
</li> </li>
<li> GNU Make is recommended, but should not be required. <li> GNU Make is required for GCC 3.4 and later.
</li> </li>
<li> The GNU Autotools are needed if you are messing with <li> The GNU Autotools are needed if you are messing with
the configury or makefiles. the configury or makefiles.
...@@ -636,26 +628,17 @@ which is no longer available, thanks deja...--> ...@@ -636,26 +628,17 @@ which is no longer available, thanks deja...-->
respond to your report. Thank you. respond to your report. Thank you.
</p> </p>
<hr />
<h2><a name="4_1">4.1 What works already?</a></h2> <h2><a name="4_1">4.1 What works already?</a></h2>
<p>Short answer: Pretty much everything <em>works</em> except for some <p>Short answer: Pretty much everything <em>works</em> except for some
corner cases. Also, localization is incomplete. For whether it works corner cases. Also, localization is incomplete. For whether it works
well, or as you expect it to work, see 5.2. well, or as you expect it to work, see 5.2.
</p> </p>
<p>Long answer: See the docs/html/17_intro/CHECKLIST file, which is <p>Long answer: See the docs/html/17_intro/CHECKLIST file, which is
badly outdated... badly outdated... Also see the RELEASE-NOTES file, which is kept
</p> more up to date.
<p>What follows is a verbatim clip from the &quot;Status&quot; section
of the RELEASE-NOTES for the latest snapshot. For a list of
fixed bugs, see that file.
</p> </p>
<!-- Yeah, I meant that "verbatim clip" thing literally... :-) -->
<pre>
New:
</pre>
<hr /> <hr />
<h2><a name="4_2">4.2 Bugs in gcc/g++ (not libstdc++-v3)</a></h2> <h2><a name="4_2">4.2 Bugs in gcc/g++ (not libstdc++-v3)</a></h2>
<p>This is by no means meant to be complete nor exhaustive, but <p>This is by no means meant to be complete nor exhaustive, but
...@@ -915,9 +898,9 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -915,9 +898,9 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
<hr /> <hr />
<h2><a name="5_3">5.3 What about the STL from SGI?</a></h2> <h2><a name="5_3">5.3 What about the STL from SGI?</a></h2>
<p>The <a href="http://www.sgi.com/tech/stl/">STL from SGI</a>, <p>The <a href="http://www.sgi.com/tech/stl/">STL from SGI</a>,
version 3.3, was the most recent merge of the STL codebase. The version 3.3, was the final merge of the STL codebase. The
code in libstdc++ contains many fixes and changes, and it is code in libstdc++ contains many fixes and changes, and
very likely that the SGI code is no longer under active 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.
</p> </p>
<p>In particular, <code>string</code> is not from SGI and makes no <p>In particular, <code>string</code> is not from SGI and makes no
......
libstdc++-v3/docs/html/faq/index.txt
#[1]GNU C++ Standard Library [2]Copyright #[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
[3]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
[4]http://gcc.gnu.org/onlinedocs/libstdc++/documentation.html. [4]http://gcc.gnu.org/onlinedocs/libstdc++/documentation.html.
To the [5]libstdc++-v3 homepage. To the [5]libstdc++-v3 homepage.
_________________________________________________________________ _________________________________________________________________
Questions Questions
1. [6]General Information 1. [6]General Information
1. [7]What is libstdc++-v3? 1. [7]What is libstdc++-v3?
2. [8]Why should I use libstdc++? 2. [8]Why should I use libstdc++?
...@@ -71,29 +71,26 @@ ...@@ -71,29 +71,26 @@
9. [57]How do I make std::vector<T>::capacity() == 9. [57]How do I make std::vector<T>::capacity() ==
std::vector<T>::size? std::vector<T>::size?
_________________________________________________________________ _________________________________________________________________
1.0 General Information 1.0 General Information
1.1 What is libstdc++-v3? 1.1 What is libstdc++-v3?
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. For those who want to see exactly how far the project has
a snapshot and released. The latest release is [58]the fourteenth come, or just want the latest bleeding-edge code, the up-to-date
snapshot but newer versions have been included in recent GCC releases. source is available over anonymous CVS, and can even be browsed over
For those who want to see exactly how far the project has come, or the Web (see [58]1.4 below).
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 [59]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. [60]If you are using V2, then been completely replaced and rewritten. [59]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
[61]design document. [60]design document.
_________________________________________________________________ _________________________________________________________________
1.2 Why should I use libstdc++? 1.2 Why should I use libstdc++?
The completion of the ISO C++ standardization gave the C++ community a The completion of the ISO C++ standardization gave the C++ community a
...@@ -101,79 +98,79 @@ ...@@ -101,79 +98,79 @@
Library. However, all existing C++ implementations are (as the Draft Library. However, all existing C++ implementations are (as the Draft
Standard used to say) "incomplet and incorrekt," and many suffer from Standard used to say) "incomplet and incorrekt," and many suffer from
limitations of the compilers that use them. limitations of the compilers that use them.
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 [62]GCC team. All of development is overseen by the [61]GCC team. All of the rapid
the rapid development and near-legendary [63]portability that are the development and near-legendary [62]portability that are the hallmarks
hallmarks of an open-source project are being applied to libstdc++. 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
string, vector<>, iostreams, and algorithms) will be freely available string, vector<>, iostreams, and algorithms) will be freely available
and fully compliant. Programmers will no longer need to "roll their and fully compliant. Programmers will no longer need to "roll their
own" nor be worried about platform-specific incompatibilities. own" nor be worried about platform-specific incompatibilities.
_________________________________________________________________ _________________________________________________________________
1.3 Who's in charge of it? 1.3 Who's in charge of it?
The libstdc++ project is contributed to by several developers all over The libstdc++ project is contributed to by several developers all over
the world, in the same way as GCC or Linux. Benjamin Kosnik, Gabriel the world, in the same way as GCC or Linux. Benjamin Kosnik, Gabriel
Dos Reis, Phil Edwards, Ulrich Drepper, Loren James Rittle, and Paolo Dos Reis, Phil Edwards, Ulrich Drepper, Loren James Rittle, and Paolo
Carlini are the lead maintainers of the CVS archive. Carlini are the lead maintainers of the CVS archive.
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 [64]homepage. everyone. You can read instructions for doing so on the [63]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 [65]homepage has instructions for retrieving the latest CVS The [64]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 [66]the Stable versions of libstdc++-v3 are included with releases of [65]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
23 through 25, mostly) is adapted from the final release of the SGI 23 through 25, mostly) is adapted from the final release of the SGI
STL. STL, with extensive changes.
_________________________________________________________________ _________________________________________________________________
1.5 When is libstdc++ going to be finished? 1.5 When is libstdc++ going to be finished?
Nathan Myers gave the best of all possible answers, responding to a Nathan Myers gave the best of all possible answers, responding to a
Usenet article asking this question: Sooner, if you help. Usenet article asking this question: Sooner, if you help.
_________________________________________________________________ _________________________________________________________________
1.6 How do I contribute to the effort? 1.6 How do I contribute to the effort?
Here is [67]a page devoted to this topic. Subscribing to the mailing Here is [66]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
is willing to help write documentation, for example, or has found a is willing to help write documentation, for example, or has found a
bug in code that we all thought was working, is more than welcome! bug in code that we all thought was working, is more than welcome!
_________________________________________________________________ _________________________________________________________________
1.7 What happened to libg++? I need that! 1.7 What happened to libg++? I need that!
The most recent libg++ README states that libg++ is no longer being The most recent libg++ README states that libg++ is no longer being
actively maintained. It should not be used for new projects, and is actively maintained. It should not be used for new projects, and is
only being kicked along to support older code. only being kicked along to support older code.
The libg++ was designed and created when there was no Standard to The libg++ was designed and created when there was no Standard to
provide guidance. Classes like linked lists are now provided for by provide guidance. Classes like linked lists are now provided for by
list<T> and do not need to be created by genclass. (For that matter, list<T> and do not need to be created by genclass. (For that matter,
templates exist now and are well-supported, whereas genclass (mostly) templates exist now and are well-supported, whereas genclass (mostly)
predates them.) predates them.)
There are other classes in libg++ that are not specified in the ISO There are other classes in libg++ that are not specified in the ISO
Standard (e.g., statistical analysis). While there are a lot of really Standard (e.g., statistical analysis). While there are a lot of really
useful things that are used by a lot of people (e.g., statistics :-), useful things that are used by a lot of people (e.g., statistics :-),
the Standards Committee couldn't include everything, and so a lot of the Standards Committee couldn't include everything, and so a lot of
those "obvious" classes didn't get included. those "obvious" classes didn't get included.
Since libstdc++ is an implementation of the Standard Library, we have Since libstdc++ is an implementation of the Standard Library, we have
no plans at this time to include non-Standard utilities in the no plans at this time to include non-Standard utilities in the
implementation, however handy they are. (The extensions provided in implementation, however handy they are. (The extensions provided in
...@@ -182,35 +179,35 @@ ...@@ -182,35 +179,35 @@
entirely plausable that the "useful stuff" from libg++ might be entirely plausable that the "useful stuff" from libg++ might be
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 [68]Boost site houses free C++ libraries that do varying things, (The [67]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 [69]GCC extensions page describes For the bold and/or desperate, the [68]GCC extensions page describes
where to find the last libg++ source. where to find the last libg++ source.
_________________________________________________________________ _________________________________________________________________
1.8 What if I have more questions? 1.8 What if I have more questions?
If you have read the README and RELEASE-NOTES files, and your question If you have read the README and RELEASE-NOTES files, and your question
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 [70]libstdc++@gcc.gnu.org. list archives); to send to the list, use [69]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 [71]Phil you have a question about a question/answer here, contact [70]Phil
Edwards or [72]Gabriel Dos Reis. Edwards or [71]Gabriel Dos Reis.
_________________________________________________________________ _________________________________________________________________
1.9 What are the license terms for libstdc++-v3? 1.9 What are the license terms for libstdc++-v3?
See [73]our license description for these and related questions. See [72]our license description for these and related questions.
_________________________________________________________________ _________________________________________________________________
2.0 Installation 2.0 Installation
2.1 How do I install libstdc++-v3? 2.1 How do I install libstdc++-v3?
Complete instructions are not given here (this is a FAQ, not an Complete instructions are not given here (this is a FAQ, not an
...@@ -219,60 +216,60 @@ ...@@ -219,60 +216,60 @@
more automated than building the GCC 2.[78] series was. If you are more automated than building the GCC 2.[78] series was. If you are
using GCC 2.95, you can still build earlier snapshots of using GCC 2.95, you can still build earlier snapshots of
libstdc++. libstdc++.
* GNU Make is recommended, but should not be required. * GNU Make is required for GCC 3.4 and later.
* 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 [74]documentation.html provides a good overview of the steps The file [73]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 [75]RELEASE-NOTES files contain the The top-level install.html and [74]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/"
directory of the distribution. directory of the distribution.
_________________________________________________________________ _________________________________________________________________
2.2 [removed] 2.2 [removed]
This question has become moot and has been removed. The stub is here This question has become moot and has been removed. The stub is here
to preserve numbering (and hence links/bookmarks). to preserve numbering (and hence links/bookmarks).
_________________________________________________________________ _________________________________________________________________
2.3 What is this CVS thing that you keep mentioning? 2.3 What is this CVS thing that you keep mentioning?
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 [76]CVS entry in the GNU free (beer), and very high quality. The [75]CVS entry in the GNU
software catalogue has a better description as well as a [77]link to software catalogue has a better description as well as a [76]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
FTP in that it allows anyone to retrieve the latest libstdc++ sources. FTP in that it allows anyone to retrieve the latest libstdc++ sources.
After the first of April, American users will have a "/pharmacy" After the first of April, American users will have a "/pharmacy"
command-line option... command-line option...
_________________________________________________________________ _________________________________________________________________
2.4 How do I know if it works? 2.4 How do I know if it works?
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 [78]here. need DejaGNU, as described [77]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
library after building and installing it, use "make check-install" library after building and installing it, use "make check-install"
instead. instead.
If you find bugs in the testsuite programs themselves, or if you think If you find bugs in the testsuite programs themselves, or if you think
of a new test program that should be added to the suite, please write of a new test program that should be added to the suite, please write
up your idea and send it to the list! up your idea and send it to the list!
_________________________________________________________________ _________________________________________________________________
2.5 This library is HUGE! And what's libsupc++? 2.5 This library is HUGE! And what's libsupc++?
Usually the size of libraries on disk isn't noticeable. When a link Usually the size of libraries on disk isn't noticeable. When a link
...@@ -283,7 +280,7 @@ ...@@ -283,7 +280,7 @@
object file is extracted. (There's nothing unique to C++ or object file is extracted. (There's nothing unique to C++ or
libstdc++-v3 about this; it's just common behavior, given here for libstdc++-v3 about this; it's just common behavior, given here for
background reasons.) background reasons.)
Some of the object files which make up libstdc++.a are rather large. Some of the object files which make up libstdc++.a are rather large.
If you create a statically-linked executable with -static, those large If you create a statically-linked executable with -static, those large
object files are suddenly part of your executable. Historically the object files are suddenly part of your executable. Historically the
...@@ -294,33 +291,33 @@ ...@@ -294,33 +291,33 @@
files in question contain template classes and template functions, files in question contain template classes and template functions,
pre-instantiated, and splitting those up causes severe maintenance pre-instantiated, and splitting those up causes severe maintenance
headaches. headaches.
It's not a bug, and it's not really a problem. Nevertheless, some It's not a bug, and it's not really a problem. Nevertheless, some
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 [79]clause 18 of the standard, support functions (those listed in [78]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 (Using gcc
specifying -lsupc++ when calling g++ for the final link step will do instead of g++ and explicitly linking in -lsupc++ for the final link
it). This library contains only those support routines, one per object step will do it). This library contains only those support routines,
file. But if you are using anything from the rest of the library, such one per object file. But if you are using anything from the rest of
as IOStreams or vectors, then you'll still need pieces from the library, such as IOStreams or vectors, then you'll still need
libstdc++.a. pieces from libstdc++.a.
The second method is one we hope to incorporate into the library build The second method is one we hope to incorporate into the library build
process. Some platforms can place each function and variable into its process. Some platforms can place each function and variable into its
own section in a .o file. The GNU linker can then perform garbage own section in a .o file. The GNU linker can then perform garbage
collection on unused sections; this reduces the situation to only collection on unused sections; this reduces the situation to only
copying needed functions into the executable, as before, but all copying needed functions into the executable, as before, but all
happens automatically. happens automatically.
Unfortunately the garbage collection in GNU ld is buggy; sections Unfortunately the garbage collection in GNU ld is buggy; sections
(corresponding to functions and variables) which are used are (corresponding to functions and variables) which are used are
mistakenly removed, leading to horrible crashes when your executable mistakenly removed, leading to horrible crashes when your executable
starts up. For the time being, this feature is not used when building starts up. For the time being, this feature is not used when building
the library. the library.
_________________________________________________________________ _________________________________________________________________
2.6 Why do I get an error saying libstdc++.so.X is missing when I run my 2.6 Why do I get an error saying libstdc++.so.X is missing when I run my
program? program?
...@@ -347,19 +344,19 @@ shared object file: No such file or directory ...@@ -347,19 +344,19 @@ shared object file: No such file or directory
LD_LIBRARY_PATH_32/LD_LIBRARY_PATH_64 for Solaris 32-/64-bit, LD_LIBRARY_PATH_32/LD_LIBRARY_PATH_64 for Solaris 32-/64-bit,
LD_LIBRARYN32_PATH/LD_LIBRARY64_PATH for Irix N32/64-bit ABIs and LD_LIBRARYN32_PATH/LD_LIBRARY64_PATH for Irix N32/64-bit ABIs and
SHLIB_PATH for HP-UX. SHLIB_PATH for HP-UX.
See the man pages for ld(1), ldd(1) and ldconfig(8) for more See the man pages for ld(1), ldd(1) and ldconfig(8) for more
information. The dynamic linker has different names on different information. The dynamic linker has different names on different
platforms but the man page is usually called something such as ld.so / platforms but the man page is usually called something such as ld.so /
rtld / dld.so. rtld / dld.so.
_________________________________________________________________ _________________________________________________________________
3.0 Platform-Specific Issues 3.0 Platform-Specific Issues
3.1 Can libstdc++-v3 be used with <my favorite compiler>? 3.1 Can libstdc++-v3 be used with <my favorite compiler>?
Probably not. Yet. Probably not. Yet.
Because GCC advances so rapidly, development and testing of libstdc++ Because GCC advances so rapidly, development and testing of libstdc++
is being done almost entirely under that compiler. If you are curious is being done almost entirely under that compiler. If you are curious
about whether other, lesser compilers (*grin*) support libstdc++, you about whether other, lesser compilers (*grin*) support libstdc++, you
...@@ -367,79 +364,79 @@ shared object file: No such file or directory ...@@ -367,79 +364,79 @@ shared object file: No such file or directory
(see above) will still require certain tools, however. Also keep in (see above) will still require certain tools, however. Also keep in
mind that building libstdc++ does not imply that your compiler will be mind that building libstdc++ does not imply that your compiler will be
able to use all of the features found in the C++ Standard Library. able to use all of the features found in the C++ Standard Library.
Since the goal of ISO Standardization is for all C++ implementations Since the goal of ISO Standardization is for all C++ implementations
to be able to share code, the final libstdc++ should, in theory, be to be able to share code, the final libstdc++ should, in theory, be
usable under any ISO-compliant compiler. It will still be targeted and usable under any ISO-compliant compiler. It will still be targeted and
optimized for GCC/g++, however. optimized for GCC/g++, however.
_________________________________________________________________ _________________________________________________________________
3.2 [removed] 3.2 [removed]
This question has become moot and has been removed. The stub is here This question has become moot and has been removed. The stub is here
to preserve numbering (and hence links/bookmarks). to preserve numbering (and hence links/bookmarks).
_________________________________________________________________ _________________________________________________________________
3.3 [removed] 3.3 [removed]
This question has become moot and has been removed. The stub is here This question has become moot and has been removed. The stub is here
to preserve numbering (and hence links/bookmarks). to preserve numbering (and hence links/bookmarks).
_________________________________________________________________ _________________________________________________________________
3.4 I can't use 'long long' on Solaris 3.4 I can't use 'long long' on Solaris
By default we try to support the C99 long long type. This requires By default we try to support the C99 long long type. This requires
that certain functions from your C library be present. that certain functions from your C library be present.
Up through release 3.0.2 the tests performed were too general, and Up through release 3.0.2 the tests performed were too general, and
this feature was disabled when it did not need to be. The most this feature was disabled when it did not need to be. The most
commonly reported platform affected was Solaris. commonly reported platform affected was Solaris.
This has been fixed for 3.0.3 and onwards. This has been fixed for 3.0.3 and onwards.
_________________________________________________________________ _________________________________________________________________
3.5 _XOPEN_SOURCE / _GNU_SOURCE / etc is always defined 3.5 _XOPEN_SOURCE / _GNU_SOURCE / etc is always defined
On Solaris, g++ (but not gcc) always defines the preprocessor macro On Solaris, g++ (but not gcc) always defines the preprocessor macro
_XOPEN_SOURCE. On GNU/Linux, the same happens with _GNU_SOURCE. (This _XOPEN_SOURCE. On GNU/Linux, the same happens with _GNU_SOURCE. (This
is not an exhaustive list; other macros and other platforms are also is not an exhaustive list; other macros and other platforms are also
affected.) affected.)
These macros are typically used in C library headers, guarding new These macros are typically used in C library headers, guarding new
versions of functions from their older versions. The C++ standard versions of functions from their older versions. The C++ standard
library includes the C standard library, but it requires the C90 library includes the C standard library, but it requires the C90
version, which for backwards-compatability reasons is often not the version, which for backwards-compatability reasons is often not the
default for many vendors. default for many vendors.
More to the point, the C++ standard requires behavior which is only More to the point, the C++ standard requires behavior which is only
available on certain platforms after certain symbols are defined. available on certain platforms after certain symbols are defined.
Usually the issue involves I/O-related typedefs. In order to ensure Usually the issue involves I/O-related typedefs. In order to ensure
correctness, the compiler simply predefines those symbols. correctness, the compiler simply predefines those symbols.
Note that it's not enough to #define them only when the library is Note that it's not enough to #define them only when the library is
being built (during installation). Since we don't have an 'export' being built (during installation). Since we don't have an 'export'
keyword, much of the library exists as headers, which means that the keyword, much of the library exists as headers, which means that the
symbols must also be defined as your programs are parsed and compiled. symbols must also be defined as your programs are parsed and compiled.
To see which symbols are defined, look for CPLUSPLUS_CPP_SPEC in the To see which symbols are defined, look for CPLUSPLUS_CPP_SPEC in the
gcc config headers for your target (and try changing them to see what gcc config headers for your target (and try changing them to see what
happens when building complicated code). You can also run "g++ -E -dM happens when building complicated code). You can also run "g++ -E -dM
- < /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 [80]quite a bit. This has been discussed on the mailing lists [79]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.
_________________________________________________________________ _________________________________________________________________
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. [81]Here's a link to the patch is quite simple, and well-known. [80]Here's a link to the
solution. solution.
_________________________________________________________________ _________________________________________________________________
3.7 Threading is broken on i386 3.7 Threading is broken on i386
Support for atomic integer operations is/was broken on i386 platforms. Support for atomic integer operations is/was broken on i386 platforms.
...@@ -448,10 +445,10 @@ shared object file: No such file or directory ...@@ -448,10 +445,10 @@ shared object file: No such file or directory
i386-linux, but actually used the programs on an i686, then you would i386-linux, but actually used the programs on an i686, then you would
encounter no problems. Only when actually running the code on a i386 encounter no problems. Only when actually running the code on a i386
will the problem appear. will the problem appear.
This is fixed in 3.2.2. This is fixed in 3.2.2.
_________________________________________________________________ _________________________________________________________________
3.8 Recent GNU/Linux glibc required? 3.8 Recent GNU/Linux glibc required?
When running on GNU/Linux, libstdc++ 3.2.1 (shared library version When running on GNU/Linux, libstdc++ 3.2.1 (shared library version
...@@ -459,12 +456,12 @@ shared object file: No such file or directory ...@@ -459,12 +456,12 @@ shared object file: No such file or directory
C library (glibc) version 2.2.5. That version of glibc is over a year C library (glibc) version 2.2.5. That version of glibc is over a year
old and contains necessary bugfixes. Many GNU/Linux distros make glibc old and contains necessary bugfixes. Many GNU/Linux distros make glibc
version 2.3.x available now. version 2.3.x available now.
The guideline is simple: the more recent the C++ library, the more The guideline is simple: the more recent the C++ library, the more
recent the C library. (This is also documented in the main GCC recent the C library. (This is also documented in the main GCC
installation instructions.) installation instructions.)
_________________________________________________________________ _________________________________________________________________
3.9 Can't use wchar_t/wstring on FreeBSD 3.9 Can't use wchar_t/wstring on FreeBSD
At the moment there are a few problems in FreeBSD's support for wide At the moment there are a few problems in FreeBSD's support for wide
...@@ -472,111 +469,108 @@ shared object file: No such file or directory ...@@ -472,111 +469,108 @@ shared object file: No such file or directory
that wchar_t support should be disabled. Once the underlying problems that wchar_t support should be disabled. Once the underlying problems
are fixed in FreeBSD (soon), the library support will automatically are fixed in FreeBSD (soon), the library support will automatically
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 [82]this short thread ("_GLIBCPP_USE_WCHAR_T undefined in by reading [81]this short thread ("_GLIBCPP_USE_WCHAR_T undefined in
FreeBSD's c++config.h?"). FreeBSD's c++config.h?").
_________________________________________________________________ _________________________________________________________________
3.10 MIPS atomic operations 3.10 MIPS atomic operations
The atomic locking routines for MIPS targets requires MIPS II and The atomic locking routines for MIPS targets requires MIPS II and
later. A patch went in just after the 3.3 release to make mips* use later. A patch went in just after the 3.3 release to make mips* use
the generic implementation instead. You can also configure for the generic implementation instead. You can also configure for
mipsel-elf as a workaround. mipsel-elf as a workaround.
mips*-*-linux* continues to use the MIPS II routines, and more work in mips*-*-linux* continues to use the MIPS II routines, and more work in
this area is expected. 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
of an open-source project. For the latest information, join the of an open-source project. For the latest information, join the
mailing list or look through recent archives. The RELEASE- NOTES and mailing list or look through recent archives. The RELEASE- NOTES and
BUGS files are generally kept up-to-date. BUGS files are generally kept up-to-date.
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 [83]the configuration instructions for GCC, being found. Please read [82]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.
This was fixed for 3.0.2. This was fixed for 3.0.2.
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 [84]the installation instructions for GCC, token." Please read [83]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
releases). releases).
Please do not report these as bugs. We know about them. Reporting this Please do not report these as bugs. We know about them. Reporting this
-- or any other problem that's already been fixed -- hinders the -- or any other problem that's already been fixed -- hinders the
development of GCC, because we have to take time to respond to your development of GCC, because we have to take time to respond to your
report. Thank you. report. Thank you.
_________________________________________________________________
4.1 What works already? 4.1 What works already?
Short answer: Pretty much everything works except for some corner Short answer: Pretty much everything works except for some corner
cases. Also, localization is incomplete. For whether it works well, or cases. Also, localization is incomplete. For whether it works well, or
as you expect it to work, see 5.2. as you expect it to work, see 5.2.
Long answer: See the docs/html/17_intro/CHECKLIST file, which is badly Long answer: See the docs/html/17_intro/CHECKLIST file, which is badly
outdated... outdated... Also see the RELEASE-NOTES file, which is kept more up to
date.
What follows is a verbatim clip from the "Status" section of the
RELEASE-NOTES for the latest snapshot. For a list of fixed bugs, see
that file.
New:
_________________________________________________________________ _________________________________________________________________
4.2 Bugs in gcc/g++ (not libstdc++-v3) 4.2 Bugs in gcc/g++ (not libstdc++-v3)
This is by no means meant to be complete nor exhaustive, but mentions This is by no means meant to be complete nor exhaustive, but mentions
some problems that users may encounter when building or using some problems that users may encounter when building or using
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 [85]bugs database with the Before reporting a bug, examine the [84]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, [86]changing your GDB settings can default on your platform. Also, [85]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 [87]message to the list, Yes, unfortunately, there are some. In a [86]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 [88]posted on his website. concern the library. The list itself is [87]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 [89]here. public list of the library defects is occasionally published [88]here.
Some of these have resulted in [90]code changes. Some of these have resulted in [89]code changes.
_________________________________________________________________ _________________________________________________________________
4.4 Things in libstdc++ that only look like bugs 4.4 Things in libstdc++ that only look like bugs
There are things which are not bugs in the compiler (4.2) nor the There are things which are not bugs in the compiler (4.2) nor the
language specification (4.3), but aren't really bugs in libstdc++, language specification (4.3), but aren't really bugs in libstdc++,
either. Really! Please do not report these as bugs. either. Really! Please do not report these as bugs.
-Weffc++ The biggest of these is the quadzillions of warnings about -Weffc++ The biggest of these is the quadzillions of warnings about
the library headers emitted when -Weffc++ is used. Making libstdc++ the library headers emitted when -Weffc++ is used. Making libstdc++
"-Weffc++-clean" is not a goal of the project, for a few reasons. "-Weffc++-clean" is not a goal of the project, for a few reasons.
Mainly, that option tries to enforce object-oriented programming, Mainly, that option tries to enforce object-oriented programming,
while the Standard Library isn't necessarily trying to be OO. while the Standard Library isn't necessarily trying to be OO.
reopening a stream fails Did I just say that -Weffc++ was our biggest reopening a stream fails Did I just say that -Weffc++ was our biggest
false-bug report? I lied. (It used to be.) Today it seems to be false-bug report? I lied. (It used to be.) Today it seems to be
reports that after executing a sequence like reports that after executing a sequence like
...@@ -594,38 +588,38 @@ New: ...@@ -594,38 +588,38 @@ 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 [91]proposed LWG resolution in DR #22 is to leave the flags the [90]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.
rel_ops Another is the rel_ops namespace and the template comparison rel_ops Another is the rel_ops namespace and the template comparison
operator functions contained therein. If they become visible in the operator functions contained therein. If they become visible in the
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 [92]sums things up here. The collisions with Nathan Myers [91]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
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 [93]the GCC bug database). paragraph of the page describing [92]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,
then you are using the old libstdc++-v2 library, which is nonstandard then you are using the old libstdc++-v2 library, which is nonstandard
and unmaintained. Do not report problems with -v2 to the -v3 mailing and unmaintained. Do not report problems with -v2 to the -v3 mailing
list. list.
For GCC versions 3.0 and 3.1 the libstdc++-v3 header files are For GCC versions 3.0 and 3.1 the libstdc++-v3 header files are
installed in ${prefix}/include/g++-v3 (see the 'v'?). Starting with installed in ${prefix}/include/g++-v3 (see the 'v'?). Starting with
version 3.2 the headers are installed in version 3.2 the headers are installed in
${prefix}/include/c++/${version} as this prevents headers from ${prefix}/include/c++/${version} as this prevents headers from
previous versions being found by mistake. previous versions being found by mistake.
glibc If you're on a GNU/Linux system and have just upgraded to glibc 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 2.2, but are still using gcc 2.95.2, then you should have read the
glibc FAQ, specifically 2.34: glibc FAQ, specifically 2.34:
...@@ -637,10 +631,10 @@ type has changed in glibc 2.2. The patch is at ...@@ -637,10 +631,10 @@ 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 [94]old v2 library which is no Note that 2.95.x shipped with the [93]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.
concept checks If you see compilation errors containing messages about concept checks If you see compilation errors containing messages about
fooConcept and a constraints member function, then most likely you fooConcept and a constraints member function, then most likely you
have violated one of the requirements for types used during have violated one of the requirements for types used during
...@@ -648,10 +642,10 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -648,10 +642,10 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
EqualityComparableConcept appears if your types must be comparable EqualityComparableConcept appears if your types must be comparable
with == and you have not provided this capability (a typo, or wrong with == and you have not provided this capability (a typo, or wrong
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 [95]here. checks, is available [94]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
correct options when compiling and linking: correct options when compiling and linking:
...@@ -669,50 +663,50 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -669,50 +663,50 @@ 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 [96]valgrind. The library's default allocators keep checkers such as [95]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 [97]Tips for want to test the library for memory leaks please read [96]Tips for
memory leak hunting first. memory leak hunting first.
_________________________________________________________________ _________________________________________________________________
4.5 Aw, that's easy to fix! 4.5 Aw, that's easy to fix!
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
[98]submitting patches that covers the procedure, but for libstdc++ [97]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++ [99]contributors' page also GCC patches mailing list. The libstdc++ [98]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 [100]testsuite -- but only if such a test caught immediately by the [99]testsuite -- but only if such a test
exists. exists.
_________________________________________________________________ _________________________________________________________________
5.0 Miscellaneous 5.0 Miscellaneous
5.1 string::iterator is not char*; vector<T>::iterator is not T* 5.1 string::iterator is not char*; vector<T>::iterator is not T*
If you have code that depends on container<T> iterators being If you have code that depends on container<T> iterators being
implemented as pointer-to-T, your code is broken. implemented as pointer-to-T, your code is broken.
While there are arguments for iterators to be implemented in that While there are arguments for iterators to be implemented in that
manner, A) they aren't very good ones in the long term, and B) they manner, A) they aren't very good ones in the long term, and B) they
were never guaranteed by the Standard anyway. The type-safety achieved were never guaranteed by the Standard anyway. The type-safety achieved
by making iterators a real class rather than a typedef for T* by making iterators a real class rather than a typedef for T*
outweighs nearly all opposing arguments. outweighs nearly all opposing arguments.
Code which does assume that a vector iterator i is a pointer can often Code which does assume that a vector iterator i is a pointer can often
be fixed by changing i in certain expressions to &*i . Future be fixed by changing i in certain expressions to &*i . Future
revisions of the Standard are expected to bless this usage for revisions of the Standard are expected to bless this usage for
vector<> (but not for basic_string<>). vector<> (but not for basic_string<>).
_________________________________________________________________ _________________________________________________________________
5.2 What's next after libstdc++-v3? 5.2 What's next after libstdc++-v3?
Hopefully, not much. The goal of libstdc++-v3 is to produce a Hopefully, not much. The goal of libstdc++-v3 is to produce a
...@@ -724,7 +718,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -724,7 +718,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 [101]the resolution specifies. Those additions are listed in [100]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
...@@ -739,27 +733,27 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -739,27 +733,27 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
they seem to be "standard" enough. (For example, the "long long" they seem to be "standard" enough. (For example, the "long long"
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.
[102]This question about the next libstdc++ prompted some brief but [101]This question about the next libstdc++ prompted some brief but
interesting [103]speculation. interesting [102]speculation.
_________________________________________________________________ _________________________________________________________________
5.3 What about the STL from SGI? 5.3 What about the STL from SGI?
The [104]STL from SGI, version 3.3, was the most recent merge of the The [103]STL from SGI, version 3.3, was the final merge of the STL
STL codebase. The code in libstdc++ contains many fixes and changes, codebase. The code in libstdc++ contains many fixes and changes, and
and it is very likely that the SGI code is no longer under active the SGI code is no longer under active development. We expect that no
development. We expect that no future merges will take place. future merges will take place.
In particular, string is not from SGI and makes no use of their "rope" In particular, string is not from SGI and makes no use of their "rope"
class (which is included as an optional extension), nor is valarray class (which is included as an optional extension), nor is valarray
and some others. Classes like vector<> are, however we have made and some others. Classes like vector<> are, however we have made
significant changes to them since then. significant changes to them since then.
The FAQ for SGI's STL (one jump off of their main page) is recommended The FAQ for SGI's STL (one jump off of their main page) is recommended
reading. reading.
_________________________________________________________________ _________________________________________________________________
5.4 Extensions and Backward Compatibility 5.4 Extensions and Backward Compatibility
Headers in the ext and backward subdirectories should be referred to Headers in the ext and backward subdirectories should be referred to
...@@ -770,7 +764,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -770,7 +764,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
forward-compatible. (The situation is the same as that of other forward-compatible. (The situation is the same as that of other
headers whose directories are not searched directly, e.g., headers whose directories are not searched directly, e.g.,
<sys/stat.h>, <X11/Xlib.h>. <sys/stat.h>, <X11/Xlib.h>.
The extensions are no longer in the global or std namespaces, instead The extensions are no longer in the global or std namespaces, instead
they are declared in the __gnu_cxx namespace. For maximum portability, they are declared in the __gnu_cxx namespace. For maximum portability,
consider defining a namespace alias to use to talk about extensions, consider defining a namespace alias to use to talk about extensions,
...@@ -795,20 +789,20 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -795,20 +789,20 @@ 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.
Note: explicit template specializations must be declared in the same Note: explicit template specializations must be declared in the same
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 [105]their own page. Extensions to the library have [104]their own page.
_________________________________________________________________ _________________________________________________________________
5.5 [removed] 5.5 [removed]
This question has become moot and has been removed. The stub is here This question has become moot and has been removed. The stub is here
to preserve numbering (and hence links/bookmarks). to preserve numbering (and hence links/bookmarks).
_________________________________________________________________ _________________________________________________________________
5.6 Is libstdc++-v3 thread-safe? 5.6 Is libstdc++-v3 thread-safe?
libstdc++-v3 strives to be thread-safe when all of the following libstdc++-v3 strives to be thread-safe when all of the following
...@@ -817,7 +811,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -817,7 +811,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
* gcc -v reports a thread model other than 'single', * gcc -v reports a thread model other than 'single',
* [pre-3.3 only] a non-generic implementation of atomicity.h exists * [pre-3.3 only] a non-generic implementation of atomicity.h exists
for the architecture in question. for the architecture in question.
The user-code must guard against concurrent method calls which may The user-code must guard against concurrent method calls which may
access any particular library object's state. Typically, the access any particular library object's state. Typically, the
application programmer may infer what object locks must be held based application programmer may infer what object locks must be held based
...@@ -852,11 +846,11 @@ a ...@@ -852,11 +846,11 @@ a
both read and write access to objects; unless otherwise documented as both read and write access to objects; unless otherwise documented as
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 [106]17 (library introduction), [107]23 (containers), and See chapters [105]17 (library introduction), [106]23 (containers), and
[108]27 (I/O) for more information. [107]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?
Copies of the full ISO 14882 standard are available on line via the Copies of the full ISO 14882 standard are available on line via the
...@@ -865,14 +859,14 @@ a ...@@ -865,14 +859,14 @@ 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 [109]here. (And if you've already registered with them, clicking right [108]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
[110]buy the standard on-line. [109]buy the standard on-line.
Who is your country's member body? Visit the [111]ISO homepage and Who is your country's member body? Visit the [110]ISO homepage and
find out! find out!
_________________________________________________________________ _________________________________________________________________
5.8 What's an ABI and why is it so messy? 5.8 What's an ABI and why is it so messy?
"ABI" stands for "Application Binary Interface." Conventionally, it "ABI" stands for "Application Binary Interface." Conventionally, it
...@@ -885,7 +879,7 @@ a ...@@ -885,7 +879,7 @@ a
one ABI and all the OSes and compilers use it. In practice every ABI one ABI and all the OSes and compilers use it. In practice every ABI
omits details that compiler implementers (consciously or accidentally) omits details that compiler implementers (consciously or accidentally)
must choose for themselves. must choose for themselves.
That ABI definition suffices for compilers to generate code so a That ABI definition suffices for compilers to generate code so a
program can interact safely with an OS and its lowest-level libraries. program can interact safely with an OS and its lowest-level libraries.
Users usually want an ABI to encompass more detail, allowing libraries Users usually want an ABI to encompass more detail, allowing libraries
...@@ -898,7 +892,7 @@ a ...@@ -898,7 +892,7 @@ a
C++, and is immediately useful for embedded work relying only on a C++, and is immediately useful for embedded work relying only on a
"free-standing implementation" that doesn't include (much of) the "free-standing implementation" that doesn't include (much of) the
standard library. It is a good basis for the work to come. standard library. It is a good basis for the work to come.
A useful C++ ABI must also incorporate many details of the standard A useful C++ ABI must also incorporate many details of the standard
library implementation. For a C ABI, the layouts of a few structs library implementation. For a C ABI, the layouts of a few structs
(such as FILE, stat, jmpbuf, and the like) and a few macros suffice. (such as FILE, stat, jmpbuf, and the like) and a few macros suffice.
...@@ -910,7 +904,7 @@ a ...@@ -910,7 +904,7 @@ a
documenting library implementation details, but carefully designing documenting library implementation details, but carefully designing
those details so that future bug fixes and optimizations don't force those details so that future bug fixes and optimizations don't force
breaking the ABI. breaking the ABI.
There are ways to help isolate library implementation details from the There are ways to help isolate library implementation details from the
ABI, but they trade off against speed. Library details used in inner ABI, but they trade off against speed. Library details used in inner
loops (e.g., getchar) must be exposed and frozen for all time, but loops (e.g., getchar) must be exposed and frozen for all time, but
...@@ -919,7 +913,7 @@ a ...@@ -919,7 +913,7 @@ a
happen before you can reasonably document a candidate C++ ABI that happen before you can reasonably document a candidate C++ ABI that
encompasses the standard library. encompasses the standard library.
_________________________________________________________________ _________________________________________________________________
5.9 How do I make std::vector<T>::capacity() == std::vector<T>::size()? 5.9 How do I make std::vector<T>::capacity() == std::vector<T>::size()?
The standard idiom for deallocating a std::vector<T>'s unused memory The standard idiom for deallocating a std::vector<T>'s unused memory
...@@ -929,12 +923,12 @@ a ...@@ -929,12 +923,12 @@ a
The copy will take O(n) time and the swap is constant time. The copy will take O(n) time and the swap is constant time.
See [112]Shrink-to-fit strings for a similar solution for strings. See [111]Shrink-to-fit strings for a similar solution for strings.
_________________________________________________________________ _________________________________________________________________
See [113]license.html for copying conditions. Comments and suggestions See [112]license.html for copying conditions. Comments and suggestions
are welcome, and may be sent to [114]the libstdc++ mailing list. are welcome, and may be sent to [113]the libstdc++ mailing list.
References References
...@@ -995,60 +989,59 @@ References ...@@ -995,60 +989,59 @@ References
55. ../faq/index.html#5_7 55. ../faq/index.html#5_7
56. ../faq/index.html#5_8 56. ../faq/index.html#5_8
57. ../faq/index.html#5_9 57. ../faq/index.html#5_9
58. http://gcc.gnu.org/libstdc++/index.html#download 58. ../faq/index.html#1_4
59. ../faq/index.html#1_4 59. ../faq/index.html#4_4_interface
60. ../faq/index.html#4_4_interface 60. ../17_intro/DESIGN
61. ../17_intro/DESIGN 61. http://gcc.gnu.org/
62. http://gcc.gnu.org/ 62. http://gcc.gnu.org/gcc-3.3/buildstat.html
63. http://gcc.gnu.org/gcc-3.0/buildstat.html 63. http://gcc.gnu.org/libstdc++/
64. http://gcc.gnu.org/libstdc++/ 64. http://gcc.gnu.org/libstdc++/
65. http://gcc.gnu.org/libstdc++/ 65. http://gcc.gnu.org/releases.html
66. http://gcc.gnu.org/releases.html 66. ../17_intro/contribute.html
67. ../17_intro/contribute.html 67. http://www.boost.org/
68. http://www.boost.org/ 68. http://gcc.gnu.org/extensions.html
69. http://gcc.gnu.org/extensions.html 69. mailto:libstdc++@gcc.gnu.org
70. mailto:libstdc++@gcc.gnu.org 70. mailto:pme@gcc.gnu.org
71. mailto:pme@gcc.gnu.org 71. mailto:gdr@gcc.gnu.org
72. mailto:gdr@gcc.gnu.org 72. ../17_intro/license.html
73. ../17_intro/license.html 73. ../documentation.html
74. ../documentation.html 74. ../17_intro/RELEASE-NOTES
75. ../17_intro/RELEASE-NOTES 75. http://www.gnu.org/software/cvs/cvs.html
76. http://www.gnu.org/software/cvs/cvs.html 76. http://www.cvshome.org/
77. http://www.cvshome.org/ 77. http://gcc.gnu.org/install/test.html
78. http://gcc.gnu.org/install/test.html 78. ../18_support/howto.html
79. ../18_support/howto.html 79. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
80. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris 80. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
81. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html 81. http://gcc.gnu.org/ml/libstdc++/2003-02/subjects.html#00286
82. http://gcc.gnu.org/ml/libstdc++/2003-02/subjects.html#00286 82. http://gcc.gnu.org/install/configure.html
83. http://gcc.gnu.org/install/configure.html 83. http://gcc.gnu.org/install/
84. http://gcc.gnu.org/install/ 84. http://gcc.gnu.org/bugs.html
85. http://gcc.gnu.org/bugs.html 85. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
86. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html 86. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
87. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html 87. http://www.cantrip.org/draft-bugs.txt
88. http://www.cantrip.org/draft-bugs.txt 88. http://anubis.dkuug.dk/jtc1/sc22/wg21/
89. http://anubis.dkuug.dk/jtc1/sc22/wg21/ 89. ../faq/index.html#5_2
90. ../faq/index.html#5_2 90. ../ext/howto.html#5
91. ../ext/howto.html#5 91. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
92. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html 92. http://gcc.gnu.org/bugs.html
93. http://gcc.gnu.org/gnatswrite.html 93. ../faq/index.html#4_4_interface
94. ../faq/index.html#4_4_interface 94. ../19_diagnostics/howto.html#3
95. ../19_diagnostics/howto.html#3 95. http://developer.kde.org/~sewardj/
96. http://developer.kde.org/~sewardj/ 96. ../debug.html#mem
97. ../debug.html#mem 97. http://gcc.gnu.org/contribute.html
98. http://gcc.gnu.org/contribute.html 98. ../17_intro/contribute.html
99. ../17_intro/contribute.html 99. ../faq/index.html#2_4
100. ../faq/index.html#2_4 100. ../ext/howto.html#5
101. ../ext/howto.html#5 101. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
102. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html 102. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
103. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html 103. http://www.sgi.com/tech/stl/
104. http://www.sgi.com/tech/stl/ 104. ../ext/howto.html
105. ../ext/howto.html 105. ../17_intro/howto.html#3
106. ../17_intro/howto.html#3 106. ../23_containers/howto.html#3
107. ../23_containers/howto.html#3 107. ../27_io/howto.html#9
108. ../27_io/howto.html#9 108. http://www.ansi.org/
109. http://www.ansi.org/ 109. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%3A2003
110. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 110. http://www.iso.ch/
111. http://www.iso.ch/ 111. ../21_strings/howto.html#6
112. ../21_strings/howto.html#6 112. ../17_intro/license.html
113. ../17_intro/license.html 113. mailto:libstdc++@gcc.gnu.org
114. 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