This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
wwwdocs PATCH: more libstdc++ restructuring
- To: gcc-patches at gcc dot gnu dot org
- Subject: wwwdocs PATCH: more libstdc++ restructuring
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Thu, 16 Nov 2000 20:32:06 -0500
- Cc: libstdc++ at sources dot redhat dot com
This just about completes the "make v3 pages work happily with wwwdocs"
work that Gerald and I have been planning. Installed.
Phil
"planning"... hahahahaha, like we had a "plan" of some kind...
2000-11-16 Phil Edwards <pme@sources.redhat.com>
* header.ihtml: Move main body tags out of here...
* footer.ihtml: ...and here...
* documentation.html: ...into here,
* download.html: and here,
* index.html: and here,
* links.html: and here,
* mail.html: and here,
* status.html: and here,
* thanks.html: and here.
* faq/index.html: Update for v3-is-the-default and 2.91 snapshot.
* faq/index.txt: Regenerated.
Index: documentation.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/documentation.html,v
retrieving revision 1.6
diff -u -3 -r1.6 documentation.html
--- documentation.html 2000/11/16 20:59:15 1.6
+++ documentation.html 2000/11/17 01:17:54
@@ -1,3 +1,12 @@
+<HTML>
+<HEAD>
+ <META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
+ <TITLE>Standard C++ Library v3</TITLE>
+<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
+<LINK REL=StyleSheet HREF="lib3styles.css">
+<!-- $Id: header.ihtml,v 1.1 2000/11/16 20:59:15 pme Exp $ -->
+</HEAD>
+<BODY>
<!--#include virtual="/libstdc++/header.ihtml"-->
Index: download.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/download.html,v
retrieving revision 1.9
diff -u -3 -r1.9 download.html
--- download.html 2000/11/16 20:59:15 1.9
+++ download.html 2000/11/17 01:17:54
@@ -1,3 +1,12 @@
+<HTML>
+<HEAD>
+ <META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
+ <TITLE>Standard C++ Library v3</TITLE>
+<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
+<LINK REL=StyleSheet HREF="lib3styles.css">
+<!-- $Id: header.ihtml,v 1.1 2000/11/16 20:59:15 pme Exp $ -->
+</HEAD>
+<BODY>
<!--#include virtual="/libstdc++/header.ihtml"-->
@@ -41,4 +50,6 @@
<!--#include virtual="/libstdc++/footer.ihtml"-->
+</BODY>
+</HTML>
Index: footer.ihtml
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/footer.ihtml,v
retrieving revision 1.1
diff -u -3 -r1.1 footer.ihtml
--- footer.ihtml 2000/11/16 20:59:15 1.1
+++ footer.ihtml 2000/11/17 01:17:54
@@ -13,6 +13,6 @@
2000-11-16.
</EM></P>
-<!-- And this closes everything out. -->
-<!--**POUND SIGN REMOVED**include virtual="/include/footer-subpages.html"-->
+<!-- ####################################################### -->
+
Index: header.ihtml
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/header.ihtml,v
retrieving revision 1.2
diff -u -3 -r1.2 header.ihtml
--- header.ihtml 2000/11/16 22:19:52 1.2
+++ header.ihtml 2000/11/17 01:17:54
@@ -1,16 +1,6 @@
-<HTML>
-<HEAD>
- <META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
- <TITLE>Standard C++ Library v3</TITLE>
-<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
-<LINK REL=StyleSheet HREF="lib3styles.css">
-<!-- $Id: header.ihtml,v 1.2 2000/11/16 22:19:52 gerald Exp $ -->
-</HEAD>
-<!-- This does the BODY tag and that funky imagemap. -->
-<!--**POUND SIGN REMOVED**include virtual="/include/header-subpages.html"-->
-
+<!-- ####################################################### -->
<!-- Encloses everything. :-( First row is the sigil; second row
is the rest of the page (which is another table, blech). That
second row contains two elements; the first is the TOC (in gray)
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/index.html,v
retrieving revision 1.4
diff -u -3 -r1.4 index.html
--- index.html 2000/11/16 20:59:15 1.4
+++ index.html 2000/11/17 01:17:54
@@ -1,3 +1,12 @@
+<HTML>
+<HEAD>
+ <META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
+ <TITLE>Standard C++ Library v3</TITLE>
+<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
+<LINK REL=StyleSheet HREF="lib3styles.css">
+<!-- $Id: header.ihtml,v 1.1 2000/11/16 20:59:15 pme Exp $ -->
+</HEAD>
+<BODY>
<!--#include virtual="/libstdc++/header.ihtml"-->
Index: links.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/links.html,v
retrieving revision 1.3
diff -u -3 -r1.3 links.html
--- links.html 2000/11/16 20:59:15 1.3
+++ links.html 2000/11/17 01:17:54
@@ -1,3 +1,12 @@
+<HTML>
+<HEAD>
+ <META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
+ <TITLE>Standard C++ Library v3</TITLE>
+<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
+<LINK REL=StyleSheet HREF="lib3styles.css">
+<!-- $Id: header.ihtml,v 1.1 2000/11/16 20:59:15 pme Exp $ -->
+</HEAD>
+<BODY>
<!--#include virtual="/libstdc++/header.ihtml"-->
Index: mail.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/mail.html,v
retrieving revision 1.4
diff -u -3 -r1.4 mail.html
--- mail.html 2000/11/16 20:59:15 1.4
+++ mail.html 2000/11/17 01:17:54
@@ -1,3 +1,12 @@
+<HTML>
+<HEAD>
+ <META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
+ <TITLE>Standard C++ Library v3</TITLE>
+<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
+<LINK REL=StyleSheet HREF="lib3styles.css">
+<!-- $Id: header.ihtml,v 1.1 2000/11/16 20:59:15 pme Exp $ -->
+</HEAD>
+<BODY>
<!--#include virtual="/libstdc++/header.ihtml"-->
Index: status.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/status.html,v
retrieving revision 1.3
diff -u -3 -r1.3 status.html
--- status.html 2000/11/16 20:59:15 1.3
+++ status.html 2000/11/17 01:17:54
@@ -1,3 +1,12 @@
+<HTML>
+<HEAD>
+ <META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
+ <TITLE>Standard C++ Library v3</TITLE>
+<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
+<LINK REL=StyleSheet HREF="lib3styles.css">
+<!-- $Id: header.ihtml,v 1.1 2000/11/16 20:59:15 pme Exp $ -->
+</HEAD>
+<BODY>
<!--#include virtual="/libstdc++/header.ihtml"-->
Index: thanks.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/thanks.html,v
retrieving revision 1.10
diff -u -3 -r1.10 thanks.html
--- thanks.html 2000/11/16 20:59:15 1.10
+++ thanks.html 2000/11/17 01:17:54
@@ -1,3 +1,12 @@
+<HTML>
+<HEAD>
+ <META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
+ <TITLE>Standard C++ Library v3</TITLE>
+<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
+<LINK REL=StyleSheet HREF="lib3styles.css">
+<!-- $Id: header.ihtml,v 1.1 2000/11/16 20:59:15 pme Exp $ -->
+</HEAD>
+<BODY>
<!--#include virtual="/libstdc++/header.ihtml"-->
Index: faq/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/faq/index.html,v
retrieving revision 1.8
diff -u -3 -r1.8 index.html
--- index.html 2000/11/04 03:00:10 1.8
+++ index.html 2000/11/17 01:17:54
@@ -1,11 +1,8 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
- <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="FAQ for the GNU libstdc++ effort.">
- <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 FAQ</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
<LINK REL=StyleSheet HREF="../lib3styles.css">
@@ -89,13 +86,13 @@
<H1><A NAME="1_0">1.0 General Information</A></H1>
<!-- I suspect these will mostly be links to/into existing documents. -->
<H2><A NAME="1_1">1.1 What is libstdc++-v3?</A></H2>
- <P>The GNU Standard C++ Library v3, or libstdc++-2.90.x, is an
+ <P>The GNU Standard C++ Library v3, or libstdc++-2.90.x/2.9x, is an
ongoing project to implement the ISO 14882 Standard C++ library
as described in chapters 17 through 27 and annex D. As the
library reaches stable plateaus, it is captured in a snapshot
and released. The current release is <A
-HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">the
- ninth snapshot</A>. For those who want to see exactly how
+HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.91.tar.gz">the
+ tenth snapshot</A>. For those who want to see exactly how
far the project has come, or just want the latest
bleeding-edge code, the up-to-date source is available over
anonymous CVS, and can even be browsed over the Web (see below).
@@ -147,8 +144,8 @@
<HR>
<H2><A NAME="1_4">1.4 How do I get libstdc++?</A></H2>
- <P>The ninth (and latest) snapshot of libstdc++-v3 is <A
-HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">
+ <P>The tenth (and latest) snapshot of libstdc++-v3 is <A
+HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.91.tar.gz">
available via ftp</A>.
</P>
<P>The <A HREF="../index.html">homepage</A>
@@ -167,8 +164,8 @@
HREF="http://www.deja.com/getdoc.xp?AN=469581698&fmt=text">a
Usenet article</A>.</P>
which is no longer available, thanks deja...-->
- <P>Nathan Myers gave the best of all possible answers in a
- Usenet article asking this question: Sooner, if you help.
+ <P>Nathan Myers gave the best of all possible answers, responding
+ to a Usenet article asking this question: Sooner, if you help.
</P>
@@ -273,16 +270,9 @@
<HR>
<H2><A NAME="2_2">2.2 Is this a drop-in replacement for the
libstdc++ that's shipped with g++?</A></H2>
- <P>Yes, as of 2.90.8, it is intended as such.</P>
- <P>The installation instructions cover this in more detail, but
- replacing the older library requires rebuilding some of the
- code that comes with g++. You will need sources for the 2.95.2
- compiler in order to build this snapshot. Building the library
- on its own and then using -I/-L will no longer work.
- </P>
- <P>After the 2.90.8 snapshot, the library sources were integrated
- into the compiler sources. Future releases of the compiler will
- ship with libstdc++-v3.
+ <P>Yes, as of 2.90.8, it is intended as such. And as of 2.91,
+ libstdc++-v3 <EM>is</EM></P> the library that's shipped with
+ g++, so much of this answer has become moot.
</P>
<HR>
@@ -309,7 +299,8 @@
<H2><A NAME="2_4">2.4 How do I know if it works?</A></H2>
<P>libstdc++-v3 comes with its own testsuite. You do not need
to actually install the library ("<TT>gmake
- install</TT>") to run the testsuite.
+ install</TT>") to run the testsuite. Note that 2.91 does
+ not use DejaGNU yet.
</P>
<P>To run the testsuite on the library after building it, use
"gmake check" while in your build directory. To run
@@ -324,11 +315,6 @@
building the test programs, and a list of the tests to be run,
respectively.
</P>
- <P>If you are using the libgcc.a-rebuilding method to enable std::
- you might find that the testsuite starts dying with nasty linker
- errors. This is symptomatic of the rebuilt libgcc.a not being
- installed; the previous one is still in use.
- </P>
<P>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, <B>please</B> write up your idea and send it to the list!
@@ -398,30 +384,7 @@
<pre>
New:
----
-- MT safe string. Supported CPUs are alpha, powerpc, x86, sparc32 and sparc64.
-- Configure support for --enable-threads=posix, as well as initial IO
- locking implementation.
-- Support for native building on Solaris 2.5.1, Solaris 2.6, Solaris
- 2.7, cygwin, [alpha, powerpc, x86]-linux, and preliminary support for
- Irix and Aix4.2, Aix 4.3 hosts.
-- --enable-namespaces is on by default.
-- Configure and Makefile support for "drop-in" replacement to
- libstdc++-v2 completed. It is now possible to bootstrap g++, and
- have g++ find libstdc++-v3 headers and libraries by default.
-- Synched with CVS egcs libio.
-- Cygwin native compiling supported.
-- Cross compiling and embedded targets (newlib) with multilibs support added.
-- SGI's strstream implementation has been added.
-- Copyright on all sources assigned to the FSF.
-- Configure, build and install documentation has been added.
-- Support to enable long long has been added.
-- More valarray improvements.
-- Extractors and inserters for std::complex have been added.
-- Extractors and inserters for void* have been fixed.
-- autoconf macros are now in _GLIBCPP_ namespace.
-- group checking for num_get implemented.
-- Many, many bug fixes.
+NEEDS WRITTEN
</pre>
@@ -434,28 +397,8 @@
the GCC mailing lists.
</P>
<UL>
- <LI>When using associative containers (like <TT>map</TT>), and
- compiling with <TT>-O3</TT> (or <TT>-finline-functions</TT>)
- and <TT>-Winline</TT>, I get a zillion errors like:
- <!-- Careful, the leading spaces in PRE show up directly. -->
- <PRE>
- .../include/g++/stl_tree.h: In function `int __black_count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)':
- .../include/g++/stl_tree.h:1045: warning: can't inline call to `int __black_count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
- .../include/g++/stl_tree.h:1053: warning: called from here
- </PRE>
- <P>This has been discussed a number of times; the problem
- is that __black_count is marked inline but is also a
- recursive function. As of 12 July 1999, it has been
- rewritten into an optimized non-recursive form, so
- fresh checkouts/releases should no longer see this warning.
- (The compiler can usually figure out how to make that
- transformation on its own.)
- </P>
-
- <LI>The reason that EGCS 1.1.2 cannot be used to build the
- library is that lookups do not work properly, and so the
- compiler will ICE when building the locale-related source
- files. This has been fixed in GCC 2.95.
+ <LI>As of 2.91, these bugs have all been fixed. We look forward
+ to new ones, well, not exactly...
</UL>
<HR>
@@ -588,19 +531,6 @@
<HR>
<H2><A NAME="5_5">5.5 Compiling with "-fnew-abi"</A></H2>
- <P>The library mostly works if you compile it (and programs you
- link with it) using "-fnew-abi -fno-honor-std" on a
- vanilla GCC compiler. However, some features, such as RTTI
- and error handlers, might not link properly with a vanilla
- libgcc built in GCC under the old ABI. If you rebuild libgcc
- using the "-f" flags above, you can get both complete
- language support and full benefits of -fnew-abi -- short
- mangled symbol names, far more efficient exception handling,
- and empty base optimization, to name a few. (Note that the
- new ABI may change from one GCC snapshot to the next, so you
- would have to rebuild all your libraries each time you get a
- new compiler snapshot.)
- </P>
<P>Towards the end of July 1999, this subject was brought up again
on the mailing list under a different name. The related
<A HREF="http://sources.redhat.com/ml/libstdc++/1999-q3/msg00066.html">thread</A>
@@ -612,7 +542,7 @@
<HR>
<H2><A NAME="5_6">5.6 Is libstdc++-v3 thread-safe?</A></H2>
- <P>Quick answer: no, as of 2.90.8 (ninth snapshot), the
+ <P>Quick answer: no, as of 2.91 (tenth snapshot), the
library is not appropriate for multithreaded access. The
string class is MT-safe.
</P>
Index: faq/index.txt
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/libstdc++/faq/index.txt,v
retrieving revision 1.9
diff -u -3 -r1.9 index.txt
--- index.txt 2000/11/16 20:59:15 1.9
+++ index.txt 2000/11/17 01:17:54
@@ -50,14 +50,14 @@
1.1 What is libstdc++-v3?
- The GNU Standard C++ Library v3, or libstdc++-2.90.x, is an ongoing
- project to implement the ISO 14882 Standard C++ library as described
- in chapters 17 through 27 and annex D. As the library reaches stable
- plateaus, it is captured in a snapshot and released. The current
- release is [35]the ninth snapshot. For those who want to see exactly
- how far the project has come, or just want the latest bleeding-edge
- code, the up-to-date source is available over anonymous CVS, and can
- even be browsed over the Web (see below).
+ The GNU Standard C++ Library v3, or libstdc++-2.90.x/2.9x, is an
+ ongoing project to implement the ISO 14882 Standard C++ library as
+ described in chapters 17 through 27 and annex D. As the library
+ reaches stable plateaus, it is captured in a snapshot and released.
+ The current release is [35]the tenth snapshot. For those who want to
+ see exactly how far the project has come, or just want the latest
+ bleeding-edge code, the up-to-date source is available over anonymous
+ CVS, and can even be browsed over the Web (see below).
A more formal description of the V3 goals can be found in the official
[36]design document.
@@ -98,7 +98,7 @@
1.4 How do I get libstdc++?
- The ninth (and latest) snapshot of libstdc++-v3 is [40]available via
+ The tenth (and latest) snapshot of libstdc++-v3 is [40]available via
ftp.
The [41]homepage has instructions for retrieving the latest CVS
@@ -111,8 +111,8 @@
1.5 When is libstdc++ going to be finished?
- Nathan Myers gave the best of all possible answers in a Usenet article
- asking this question: Sooner, if you help.
+ Nathan Myers gave the best of all possible answers, responding to a
+ Usenet article asking this question: Sooner, if you help.
_________________________________________________________________
1.6 How do I contribute to the effort?
@@ -202,17 +202,10 @@
2.2 Is this a drop-in replacement for the libstdc++ that's shipped with g++?
- Yes, as of 2.90.8, it is intended as such.
-
- The installation instructions cover this in more detail, but replacing
- the older library requires rebuilding some of the code that comes with
- g++. You will need sources for the 2.95.2 compiler in order to build
- this snapshot. Building the library on its own and then using -I/-L
- will no longer work.
-
- After the 2.90.8 snapshot, the library sources were integrated into
- the compiler sources. Future releases of the compiler will ship with
- libstdc++-v3.
+ Yes, as of 2.90.8, it is intended as such. And as of 2.91,
+ libstdc++-v3 is
+ the library that's shipped with g++, so much of this answer has become
+ moot.
_________________________________________________________________
2.3 What is this CVS thing that you keep mentioning?
@@ -233,7 +226,8 @@
2.4 How do I know if it works?
libstdc++-v3 comes with its own testsuite. You do not need to actually
- install the library ("gmake install") to run the testsuite.
+ install the library ("gmake install") to run the testsuite. Note that
+ 2.91 does not use DejaGNU yet.
To run the testsuite on the library after building it, use "gmake
check" while in your build directory. To run the testsuite on the
@@ -247,11 +241,6 @@
-mkcheckfiles.txt) contain messages from the compiler while building
the test programs, and a list of the tests to be run, respectively.
- If you are using the libgcc.a-rebuilding method to enable std:: you
- might find that the testsuite starts dying with nasty linker errors.
- This is symptomatic of the rebuilt libgcc.a not being installed; the
- previous one is still in use.
-
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
up your idea and send it to the list!
@@ -311,30 +300,7 @@
This is a verbatim clip from the "Status" section of the RELEASE-NOTES
for the latest snapshot.
New:
----
-- MT safe string. Supported CPUs are alpha, powerpc, x86, sparc32 and sparc64.
-- Configure support for --enable-threads=posix, as well as initial IO
- locking implementation.
-- Support for native building on Solaris 2.5.1, Solaris 2.6, Solaris
- 2.7, cygwin, [alpha, powerpc, x86]-linux, and preliminary support for
- Irix and Aix4.2, Aix 4.3 hosts.
-- --enable-namespaces is on by default.
-- Configure and Makefile support for "drop-in" replacement to
- libstdc++-v2 completed. It is now possible to bootstrap g++, and
- have g++ find libstdc++-v3 headers and libraries by default.
-- Synched with CVS egcs libio.
-- Cygwin native compiling supported.
-- Cross compiling and embedded targets (newlib) with multilibs support added.
-- SGI's strstream implementation has been added.
-- Copyright on all sources assigned to the FSF.
-- Configure, build and install documentation has been added.
-- Support to enable long long has been added.
-- More valarray improvements.
-- Extractors and inserters for std::complex have been added.
-- Extractors and inserters for void* have been fixed.
-- autoconf macros are now in _GLIBCPP_ namespace.
-- group checking for num_get implemented.
-- Many, many bug fixes.
+NEEDS WRITTEN
_________________________________________________________________
4.2 Bugs in gcc/g++ (not libstdc++-v3)
@@ -343,25 +309,8 @@
some problems that users may encounter when building or using
libstdc++. If you are experiencing one of these problems, you can find
more information on the libstdc++ and the GCC mailing lists.
- * When using associative containers (like map), and compiling with
- -O3 (or -finline-functions) and -Winline, I get a zillion errors
- like:
- .../include/g++/stl_tree.h: In function `int __black_count(struct __rb_tree_
-node_base *, struct __rb_tree_node_base *)':
- .../include/g++/stl_tree.h:1045: warning: can't inline call to `int __black_
-count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
- .../include/g++/stl_tree.h:1053: warning: called from here
-
- This has been discussed a number of times; the problem is that
- __black_count is marked inline but is also a recursive function.
- As of 12 July 1999, it has been rewritten into an optimized
- non-recursive form, so fresh checkouts/releases should no longer
- see this warning. (The compiler can usually figure out how to make
- that transformation on its own.)
- * The reason that EGCS 1.1.2 cannot be used to build the library is
- that lookups do not work properly, and so the compiler will ICE
- when building the locale-related source files. This has been fixed
- in GCC 2.95.
+ * As of 2.91, these bugs have all been fixed. We look forward to new
+ ones, well, not exactly...
_________________________________________________________________
4.3 Bugs in the C++ language/lib specification
@@ -475,17 +424,6 @@
5.5 Compiling with "-fnew-abi"
- The library mostly works if you compile it (and programs you link with
- it) using "-fnew-abi -fno-honor-std" on a vanilla GCC compiler.
- However, some features, such as RTTI and error handlers, might not
- link properly with a vanilla libgcc built in GCC under the old ABI. If
- you rebuild libgcc using the "-f" flags above, you can get both
- complete language support and full benefits of -fnew-abi -- short
- mangled symbol names, far more efficient exception handling, and empty
- base optimization, to name a few. (Note that the new ABI may change
- from one GCC snapshot to the next, so you would have to rebuild all
- your libraries each time you get a new compiler snapshot.)
-
Towards the end of July 1999, this subject was brought up again on the
mailing list under a different name. The related [66]thread (by the
name HOWTO-honor-std) is very instructive. More info is at the end of
@@ -496,7 +434,7 @@
5.6 Is libstdc++-v3 thread-safe?
- Quick answer: no, as of 2.90.8 (ninth snapshot), the library is not
+ Quick answer: no, as of 2.91 (tenth snapshot), the library is not
appropriate for multithreaded access. The string class is MT-safe.
This is assuming that your idea of "multithreaded" is the same as
@@ -524,7 +462,7 @@
Comments and suggestions are welcome, and may be sent to [72]Phil
Edwards or [73]Gabriel Dos Reis.
- $Id: index.txt,v 1.9 2000/11/16 20:59:15 pme Exp $
+ $Id: index.html,v 1.8 2000/11/04 03:00:10 pme Exp $
References
@@ -562,12 +500,12 @@
32. ../faq/index.html#5_5
33. ../faq/index.html#5_6
34. ../faq/index.html#5_7
- 35. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz
+ 35. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.91.tar.gz
36. ../17_intro/DESIGN
37. http://gcc.gnu.org/
38. http://gcc.gnu.org/gcc-2.95/buildstat.html
39. ../index.html
- 40. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz
+ 40. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.91.tar.gz
41. ../index.html
42. ../17_intro/contribute.html
43. http://www.boost.org/