From 572cd73ac976578951d38adf15c43d4dc9abb299 Mon Sep 17 00:00:00 2001
From: Phil Edwards
--enable-threads=LIB
- Select a threading library. As of libstdc++-v3 snapshot 2.91, - the choices are: - 'yes' for some kind of default (hmmmmm); - 'decosf1', 'irix', 'mach', 'os2', 'posix'/'pthreads' - (same thing), - 'solaris', 'win32', 'dce', or 'vxworks' to select the - corresponding interface; - and 'single', 'no', or 'none' for the null-case, - single-threaded library. -
-All of this is currently undergoing a lot of changes. As of - 2.91, 'single' and 'posix' are the only implemented - models. Default is single. +
Select a threading library. A full description is given in the + general compiler + configuration instructions.
--enable-version-specific-runtime-libs
@@ -204,6 +194,14 @@ options
porting steps, but builds only a subset of what is required by
ISO. By default, this option is on.
+
+ --enable-concept-checks
+ This turns on additional compile-time checks for instantiated + library templates, in the form of specialized templates, + described here. They + can help users discover when they break the rules of the STL, before + their programs run. +
Return to the top of the page or diff --git a/libstdc++-v3/docs/html/documentation.html b/libstdc++-v3/docs/html/documentation.html index b1ecdc4..ef81d3b 100644 --- a/libstdc++-v3/docs/html/documentation.html +++ b/libstdc++-v3/docs/html/documentation.html @@ -20,19 +20,25 @@ using the Doxygen tool. These are useful for examining the signatures of public member functions for the library classes, etc.
-- The latest collection is for the GCC 3.0 release, +
One collection is for the GCC 3.0 release,
libstdc++-doxygen-3.0.tar.gz
(3.8MB),
viewable online.
- The collection is also available in the libstdc++ snapshots directory at
- <URL:ftp://gcc.gnu.org/pub/gcc/libstdc++/>
. You will
- almost certainly need to use one of the
+ The latest collection is for the libstdc++ 3.0.95 snapshot release,
+ viewable online.
+ Other collections for 3.0.95 exist on the FTP sites, but are not
+ viewable online.
+
The collections are available in the libstdc++ snapshots directory at
+ <URL:ftp://gcc.gnu.org/pub/gcc/libstdc++/doxygen/>
.
+ You will almost certainly need to use one of the
mirror sites to download
the tarball. After unpacking, simply load
- libstdc++-doxygen-3.0/index.html
- in a browser. Feedback (and additional documentation!) is welcome.
+ libstdc++-doxygen-*/index.html
+ into a browser. Feedback (and additional documentation!) is welcome.
+
With 3.0.95, an initial set of man pages are also available in the same
+ directory as the doxygen collections. Start with Intro(3)
.
filebuf
s have another ctor with this signature:basic_filebuf(__c_file_type*, ios_base::openmode, int_type);
ios_base::openmode M
// same as all the other uses of openmode
int_type B
- // buffer size, defaults to BUFSIZ
+ // buffer size, defaults to BUFSIZ if not specified
For those wanting to use file descriptors instead of FILE*'s, I
invite you to contemplate the mysteries of C's fdopen()
.
+ filebuf
s bring
+ back an old extension: the fd()
member function. The
+ integer returned from this function can be used for whatever file
+ descriptors can be used for on your platform. Naturally, the
+ library cannot track what you do on your own with a file descriptor,
+ so if you perform any I/O directly, don't expect the library to be
+ aware of it.
Return to top of page or @@ -188,8 +196,8 @@ program: when your program's std::vector<int> gets cut in half and frees a bunch of its storage, that memory can be reused by the private std::list<WonkyWidget> brought in from a KDE library - that you linked against. And we don't have to call operator's new and - delete to pass the memory on, ether, which is a speed bonus. + that you linked against. And we don't have to call operators new and + delete to pass the memory on, either, which is a speed bonus. BUT...
What about threads? No problem: in a threadsafe environment, the diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html index f9f00a1..8771695 100644 --- a/libstdc++-v3/docs/html/faq/index.html +++ b/libstdc++-v3/docs/html/faq/index.html @@ -7,7 +7,7 @@
@@ -105,7 +105,7 @@ http://gcc.gnu.org/onlinedocs/libstdc++/faq/. library reaches stable plateaus, it is captured in a snapshot and released. The current release is the - eleventh snapshot. For those who want to see exactly how + twelfth 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). @@ -161,9 +161,9 @@ http://gcc.gnu.org/onlinedocs/libstdc++/faq/.The eleventh (and latest) snapshot of libstdc++-v3 is +
The twelfth (and latest) snapshot of libstdc++-v3 is available via - ftp. The filename is libstdc++-2.92.tar.gz. + ftp.
The homepage has instructions for retrieving the latest CVS sources, and for @@ -468,27 +468,25 @@ which is no longer available, thanks deja...-->
New: --- -- preliminary doxygen documentation has been added. Running "make - doxygen" in the libstdc++-v3 build directory will generate HTML - documentation that can be used to cross-reference names and files in - the library. -- a dejagnu based testing framework has been added -- a new implementation of the concept checking code has been ported - from the boost libraries. -- support for -fno-exceptions has been added -- stdexcept was re-written -- using deprecated or antiquated headers now gives a warning -- the stdio interface to iostreams has been tweaked, and now works - with synchronized c/c++ io -- new libsupc++ routines implementing the IA-64 C++ ABI. -- HPUX configuration files -- support for AIX added -- a lot of bugs were fixed. -- preliminary named locales implemented -- portability improvements made to generation of <limits> -- speedups to improve configuration time. -- DJGPP support added. -- support for dlopening shared libstdc++ +- add S390, m68k, x86-64 support. +- doxygen documentation has been extended, including man pages. +- verbose terminate handling has been added. +- some libsupc++ tweaks +- warnings for deprecated headers now active. +- dejagnu testsuite preliminary documentation. +- dejagnu testsuite default. +- dejagnu testsuite cross compiler, multilib safe. +- long long iostreams on by default, rework of ISO C99 support. +- iterator re-write and testsuites. +- container testsuites. +- allocator revamp and testsuites. +- more concept-checking work. +- basic_string optimization and MT fixes. +- new limits implementation. +- update -fno-exceptions code, verify it works. +- full named locale support fpr all facets, choice of gnu, + ieee_1003.1-200x (POSIX 2), or generic models. Full support depends + on target OS and underlying "C" library support.@@ -501,8 +499,9 @@ New: the GCC mailing lists.
You will need a recent version of g++ to compile the snapshot of libstdc++, such as one of the GCC 3.x snapshots (insert standard - caveat about using snapshots rather than formal releases). You - will need the full source - distribution to whatever compiler release you are using. The - GCC snapshots can be had from one of the sites on their - mirror list. + caveat about using snapshots rather than formal releases). You will + need the full source distribution to whatever compiler release you are + using. The GCC snapshots can be had from one of the sites on their + mirror list. If you are + using a 2.x compiler, see + the status page + first.
In addition, if you plan to modify the makefiles or regenerate the @@ -57,9 +59,6 @@ worries as long as the versions are correct).
-GNU Make is the only 'make' that will parse the makefiles correctly. -
-To test your build, you will need either DejaGNU 1.4 (to run
'make check'
like
the rest of GCC),
@@ -120,8 +119,9 @@
Check out or download the gcc sources: the resulting source directory
- (gcc
or gcc-3.0
, for example) is gccsrcdir.
+
Check out or download the GCC sources: the resulting source directory
+ (gcc
or gcc-3.0.3
, for example) is
+ gccsrcdir.
Once in gccsrcdir, you'll need to rename or delete the
libstdc++-v3 directory which comes with that snapshot:
@@ -145,7 +145,7 @@Configuring
If you have never done this before, you should read the basic GCC Installation - Instructions first. + Instructions first. Read all of them. Twice.
When building libstdc++-v3 you'll have to configure the entire gccsrcdir directory. The full list of libstdc++-v3 -- 2.7.4