From 6247d6df14aa7893a5eb0ca1c1e7aa4331a3e8cb Mon Sep 17 00:00:00 2001 From: Benjamin Kosnik Date: Wed, 29 Aug 2012 02:09:55 +0000 Subject: [PATCH] *: Regenerate. 2012-08-28 Benjamin Kosnik * doc/html/*: Regenerate. From-SVN: r190770 --- libstdc++-v3/ChangeLog | 4 + libstdc++-v3/doc/html/api.html | 38 +- libstdc++-v3/doc/html/bk02.html | 10 +- libstdc++-v3/doc/html/bk03.html | 10 +- libstdc++-v3/doc/html/faq.html | 298 +- libstdc++-v3/doc/html/index.html | 24 +- libstdc++-v3/doc/html/manual/abi.html | 140 +- libstdc++-v3/doc/html/manual/algorithms.html | 32 +- libstdc++-v3/doc/html/manual/api.html | 52 +- .../html/manual/appendix_contributing.html | 52 +- .../doc/html/manual/appendix_free.html | 26 +- .../doc/html/manual/appendix_gfdl.html | 48 +- .../doc/html/manual/appendix_gpl.html | 76 +- .../doc/html/manual/appendix_porting.html | 46 +- libstdc++-v3/doc/html/manual/associative.html | 30 +- libstdc++-v3/doc/html/manual/atomics.html | 28 +- libstdc++-v3/doc/html/manual/backwards.html | 100 +- .../doc/html/manual/bitmap_allocator.html | 24 +- libstdc++-v3/doc/html/manual/bk01pt02.html | 20 +- .../doc/html/manual/bk01pt02ch05s02.html | 22 +- .../doc/html/manual/bk01pt03ch17s02.html | 24 +- .../doc/html/manual/bk01pt03ch17s03.html | 28 +- .../doc/html/manual/bk01pt03ch17s04.html | 66 +- .../doc/html/manual/bk01pt03ch18s02.html | 22 +- .../doc/html/manual/bk01pt03ch18s03.html | 28 +- .../doc/html/manual/bk01pt03ch18s04.html | 36 +- .../doc/html/manual/bk01pt03ch18s05.html | 22 +- .../doc/html/manual/bk01pt03ch19s02.html | 44 +- .../doc/html/manual/bk01pt03ch19s03.html | 22 +- .../doc/html/manual/bk01pt03ch19s04.html | 22 +- .../doc/html/manual/bk01pt03ch19s05.html | 32 +- .../doc/html/manual/bk01pt03ch19s06.html | 26 +- .../doc/html/manual/bk01pt03ch19s07.html | 108 +- .../doc/html/manual/bk01pt03ch20s02.html | 20 +- .../doc/html/manual/bk01pt03ch20s03.html | 28 +- .../doc/html/manual/bk01pt03ch20s04.html | 20 +- .../doc/html/manual/bk01pt03ch20s05.html | 20 +- .../doc/html/manual/bk01pt03ch21s02.html | 54 +- .../doc/html/manual/bk01pt03ch23s02.html | 20 +- .../doc/html/manual/bk01pt03ch30s02.html | 30 +- .../doc/html/manual/bk01pt03ch30s03.html | 20 +- .../doc/html/manual/bk01pt03pr01.html | 22 +- libstdc++-v3/doc/html/manual/bk01pt04.html | 16 +- libstdc++-v3/doc/html/manual/bugs.html | 200 +- libstdc++-v3/doc/html/manual/concurrency.html | 36 +- libstdc++-v3/doc/html/manual/configure.html | 28 +- libstdc++-v3/doc/html/manual/containers.html | 36 +- .../doc/html/manual/containers_and_c.html | 18 +- libstdc++-v3/doc/html/manual/debug.html | 52 +- libstdc++-v3/doc/html/manual/debug_mode.html | 28 +- libstdc++-v3/doc/html/manual/diagnostics.html | 26 +- .../html/manual/documentation_hacking.html | 228 +- .../doc/html/manual/dynamic_memory.html | 22 +- .../doc/html/manual/ext_algorithms.html | 20 +- .../doc/html/manual/ext_compile_checks.html | 20 +- .../doc/html/manual/ext_concurrency.html | 30 +- .../doc/html/manual/ext_containers.html | 18 +- .../doc/html/manual/ext_demangling.html | 20 +- libstdc++-v3/doc/html/manual/ext_io.html | 26 +- .../doc/html/manual/ext_iterators.html | 20 +- .../doc/html/manual/ext_numerics.html | 20 +- .../doc/html/manual/ext_utilities.html | 20 +- libstdc++-v3/doc/html/manual/extensions.html | 22 +- libstdc++-v3/doc/html/manual/facets.html | 140 +- libstdc++-v3/doc/html/manual/fstreams.html | 24 +- .../generalized_numeric_operations.html | 22 +- libstdc++-v3/doc/html/manual/index.html | 38 +- libstdc++-v3/doc/html/manual/internals.html | 34 +- libstdc++-v3/doc/html/manual/intro.html | 20 +- libstdc++-v3/doc/html/manual/io.html | 24 +- libstdc++-v3/doc/html/manual/io_and_c.html | 20 +- libstdc++-v3/doc/html/manual/iterators.html | 28 +- libstdc++-v3/doc/html/manual/license.html | 168 +- .../doc/html/manual/localization.html | 54 +- libstdc++-v3/doc/html/manual/make.html | 18 +- libstdc++-v3/doc/html/manual/memory.html | 132 +- .../doc/html/manual/mt_allocator.html | 24 +- libstdc++-v3/doc/html/manual/numerics.html | 30 +- .../doc/html/manual/numerics_and_c.html | 20 +- libstdc++-v3/doc/html/manual/pairs.html | 20 +- .../doc/html/manual/parallel_mode.html | 32 +- .../policy_based_data_structures_test.html | 2652 +++++++++-------- .../html/manual/policy_data_structures.html | 306 +- .../manual/policy_data_structures_biblio.html | 42 +- .../manual/policy_data_structures_design.html | 264 +- .../manual/policy_data_structures_using.html | 78 +- .../doc/html/manual/profile_mode.html | 40 +- libstdc++-v3/doc/html/manual/setup.html | 28 +- .../doc/html/manual/source_code_style.html | 1242 ++++---- .../doc/html/manual/source_design_notes.html | 1724 +++++------ .../doc/html/manual/source_organization.html | 190 +- libstdc++-v3/doc/html/manual/status.html | 178 +- libstdc++-v3/doc/html/manual/streambufs.html | 28 +- libstdc++-v3/doc/html/manual/strings.html | 58 +- .../doc/html/manual/stringstreams.html | 18 +- libstdc++-v3/doc/html/manual/support.html | 40 +- libstdc++-v3/doc/html/manual/termination.html | 22 +- libstdc++-v3/doc/html/manual/test.html | 74 +- libstdc++-v3/doc/html/manual/traits.html | 18 +- libstdc++-v3/doc/html/manual/using.html | 22 +- .../doc/html/manual/using_concurrency.html | 50 +- .../html/manual/using_dynamic_or_shared.html | 32 +- .../doc/html/manual/using_exceptions.html | 86 +- .../doc/html/manual/using_headers.html | 36 +- .../doc/html/manual/using_macros.html | 16 +- .../doc/html/manual/using_namespaces.html | 26 +- libstdc++-v3/doc/html/manual/utilities.html | 26 +- 107 files changed, 5981 insertions(+), 4863 deletions(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index c92bbb37339..f9542ec1daa 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,7 @@ +2012-08-28 Benjamin Kosnik + + * doc/html/*: Regenerate. + 2012-08-28 Benjamin Kosnik PR libstdc++/54102 diff --git a/libstdc++-v3/doc/html/api.html b/libstdc++-v3/doc/html/api.html index a9cf17fbf7b..9209f90be69 100644 --- a/libstdc++-v3/doc/html/api.html +++ b/libstdc++-v3/doc/html/api.html @@ -1,16 +1,20 @@ - - -The GNU C++ Library API Reference
The GNU C++ Library API Reference
Prev  Next

Copyright © +The GNU C++ Library API Reference

The GNU C++ Library API Reference
Prev  Next

The GNU C++ Library API Reference

Copyright © 2008 , 2010 - FSF + FSF -

+

The GNU C++ library sources have been specially formatted so that with the proper invocation of another tool (Doxygen), a set of indexed reference material can generated from the sources files @@ -20,29 +24,29 @@ particular include file, looking at inheritance diagrams, etc.

The API documentation, rendered into HTML, can be viewed online: -

Prev Up Next
 Home 
+

Prev Up Next
 Home 
diff --git a/libstdc++-v3/doc/html/bk02.html b/libstdc++-v3/doc/html/bk02.html index f95372ebd79..c517b9632cb 100644 --- a/libstdc++-v3/doc/html/bk02.html +++ b/libstdc++-v3/doc/html/bk02.html @@ -1,3 +1,7 @@ - - -<meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"/><meta name="keywords" content=" ISO C++ , runtime , library "/><link rel="home" href="index.html" title="The GNU C++ Library"/><link rel="up" href="index.html" title="The GNU C++ Library"/><link rel="prev" href="manual/backwards.html" title="Backwards Compatibility"/><link rel="next" href="api.html" title="The GNU C++ Library API Reference"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"/></tr><tr><td align="left"><a accesskey="p" href="manual/backwards.html">Prev</a> </td><th width="60%" align="center"> </th><td align="right"> <a accesskey="n" href="api.html">Next</a></td></tr></table><hr/></div><div class="book"><div class="titlepage"><hr/></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="article"><a href="api.html">The GNU C++ Library API Reference</a></span></dt></dl></div></div><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td align="left"><a accesskey="p" href="manual/backwards.html">Prev</a> </td><td align="center"> </td><td align="right"> <a accesskey="n" href="api.html">Next</a></td></tr><tr><td align="left" valign="top">Backwards Compatibility </td><td align="center"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top"> The GNU C++ Library API Reference</td></tr></table></div></body></html> +<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>
Prev   Next

Table of Contents

The GNU C++ Library API Reference
Prev   Next
Backwards Compatibility Home The GNU C++ Library API Reference
diff --git a/libstdc++-v3/doc/html/bk03.html b/libstdc++-v3/doc/html/bk03.html index 5a73901a9c9..b5680730c1c 100644 --- a/libstdc++-v3/doc/html/bk03.html +++ b/libstdc++-v3/doc/html/bk03.html @@ -1,3 +1,7 @@ - - -<meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"/><meta name="keywords" content=" ISO C++ , runtime , library "/><link rel="home" href="index.html" title="The GNU C++ Library"/><link rel="up" href="index.html" title="The GNU C++ Library"/><link rel="prev" href="api.html" title="The GNU C++ Library API Reference"/><link rel="next" href="faq.html" title="Frequently Asked Questions"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"/></tr><tr><td align="left"><a accesskey="p" href="api.html">Prev</a> </td><th width="60%" align="center"> </th><td align="right"> <a accesskey="n" href="faq.html">Next</a></td></tr></table><hr/></div><div class="book"><div class="titlepage"><hr/></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="article"><a href="faq.html">Frequently Asked Questions</a></span></dt></dl></div></div><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td align="left"><a accesskey="p" href="api.html">Prev</a> </td><td align="center"> </td><td align="right"> <a accesskey="n" href="faq.html">Next</a></td></tr><tr><td align="left" valign="top">The GNU C++ Library API Reference </td><td align="center"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top"> Frequently Asked Questions</td></tr></table></div></body></html> +<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>
Prev   Next

Table of Contents

Frequently Asked Questions
Prev   Next
The GNU C++ Library API Reference Home Frequently Asked Questions
diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html index 1a47a5b26a2..1c7ee04bfb0 100644 --- a/libstdc++-v3/doc/html/faq.html +++ b/libstdc++-v3/doc/html/faq.html @@ -1,10 +1,14 @@ - - -Frequently Asked Questions
Frequently Asked Questions
Prev  

Copyright © +Frequently Asked Questions

Frequently Asked Questions
Prev  

Frequently Asked Questions

Copyright © 2008, 2010 - FSF -

1.1. + FSF +

1.1. What is libstdc++?
1.2. Why should I use libstdc++? @@ -18,7 +22,7 @@ What happened to the older libg++? I need that!
1.7. What if I have more questions? -
2.1. +
2.1. What are the license terms for libstdc++?
2.2. So any program which uses libstdc++ falls under the GPL? @@ -26,7 +30,7 @@ How is that different from the GNU {Lesser,Library} GPL?
2.4. I see. So, what restrictions are there on programs that use the library? -
3.1. How do I install libstdc++? +
3.1. How do I install libstdc++?
3.2. How does one get current libstdc++ sources?
3.3. How do I know if it works?
3.4. How do I insure that the dynamically linked library will be found? @@ -34,7 +38,7 @@ What's libsupc++?
3.6. This library is HUGE! -
4.1. +
4.1. Can libstdc++ be used with non-GNU compilers?
4.2. No 'long long' type on Solaris? @@ -50,13 +54,13 @@ Recent GNU/Linux glibc required?
4.8. Can't use wchar_t/wstring on FreeBSD -
5.1. +
5.1. What works already?
5.2. Bugs in the ISO C++ language or library specification
5.3. Bugs in the compiler (gcc/g++) and not libstdc++ -
6.1. +
6.1. Reopening a stream fails
6.2. -Weffc++ complains too much @@ -76,7 +80,7 @@ list::size() is O(n)!
6.9. Aw, that's easy to fix! -
7.1. +
7.1. string::iterator is not char*; vector<T>::iterator is not T*
7.2. What's next after libstdc++? @@ -91,7 +95,7 @@ What's an ABI and why is it so messy?
7.8. How do I make std::vector<T>::capacity() == std::vector<T>::size? -
1.1. +
1.1. What is libstdc++?
1.2. Why should I use libstdc++? @@ -105,19 +109,19 @@ What happened to the older libg++? I need that!
1.7. What if I have more questions? -

1.1.

+

1.1.

What is libstdc++? -

+

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 and annex D. 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 SVN, and can even be browsed over - the web. -

1.2.

+ the web. +

1.2.

Why should I use libstdc++? -

+

The completion of the ISO C++ standardization gave the C++ community a powerful set of reuseable tools in the form of the C++ Standard Library. However, all existing C++ implementations are @@ -129,9 +133,9 @@ (gcc, g++, etc) is widely considered to be one of the leading compilers in the world. Its development is overseen by the - GCC team. All of + GCC team. All of the rapid development and near-legendary - portability + portability that are the hallmarks of an open-source project are being applied to libstdc++.

@@ -141,9 +145,9 @@ vector<>, iostreams, and algorithms.) Programmers will no longer need to “roll their own” nor be worried about platform-specific incompatibilities. -

1.3.

+

1.3.

Who's in charge of it? -

+

The libstdc++ project is contributed to by several developers all over the world, in the same way as GCC or the Linux kernel. Benjamin Kosnik, Gabriel Dos Reis, Phil Edwards, Ulrich Drepper, @@ -153,17 +157,17 @@ Development and discussion is held on the libstdc++ mailing list. Subscribing to the list, or searching the list archives, is open to everyone. You can read instructions for - doing so on the homepage. + doing so on the homepage. If you have questions, ideas, code, or are just curious, sign up! -

1.4.

+

1.4.

When is libstdc++ going to be finished? -

+

Nathan Myers gave the best of all possible answers, responding to a Usenet article asking this question: Sooner, if you help. -

1.5.

+

1.5.

How do I contribute to the effort? -

+

Here is a page devoted to this topic. Subscribing to the mailing list (see above, or the homepage) is a very good idea if you have something to @@ -172,17 +176,17 @@ anybody who is willing to help write documentation, for example, or has found a bug in code that we all thought was working and is willing to provide details, is more than welcome! -

1.6.

+

1.6.

What happened to the older libg++? I need that! -

+

The most recent libg++ README states that libg++ is no longer being actively maintained. It should not be used for new projects, and is only being kicked along to support older code.

More information in the backwards compatibility documentation -

1.7.

+

1.7.

What if I have more questions? -

+

If you have read the README file, and your question 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 @@ -201,19 +205,19 @@ How is that different from the GNU {Lesser,Library} GPL?

2.4. I see. So, what restrictions are there on programs that use the library? -

2.1.

+

2.1.

What are the license terms for libstdc++? -

+

See our license description for these and related questions. -

2.2.

+

2.2.

So any program which uses libstdc++ falls under the GPL? -

+

No. The special exception permits use of the library in proprietary applications. -

2.3.

+

2.3.

How is that different from the GNU {Lesser,Library} GPL? -

+

The LGPL requires that users be able to replace the LGPL code with a modified version; this is trivial if the library in question is a C shared library. But there's no way to make that work with C++, where @@ -221,9 +225,9 @@ are expanded inside the code that uses the library. So to allow people to replace the library code, someone using the library would have to distribute their own source, rendering the LGPL equivalent to the GPL. -

2.4.

+

2.4.

I see. So, what restrictions are there on programs that use the library? -

+

None. We encourage such programs to be released as open source, but we won't punish you or sue you if you choose otherwise.

3.1. How do I install libstdc++? @@ -234,8 +238,8 @@ What's libsupc++?
3.6. This library is HUGE! -

3.1.

How do I install libstdc++? -

+

3.1.

How do I install libstdc++? +

Often libstdc++ comes pre-installed as an integral part of many existing GNU/Linux and Unix systems, as well as many embedded development tools. It may be necessary to install extra @@ -247,11 +251,11 @@ documentation for detailed instructions. You may wish to browse those files ahead of time to get a feel for what's required. -

3.2.

How does one get current libstdc++ sources? -

+

3.2.

How does one get current libstdc++ sources? +

Libstdc++ sources for all official releases can be obtained as part of the GCC sources, available from various sites and - mirrors. A full list of + mirrors. A full list of download sites is provided on the main GCC site.

Current libstdc++ sources can always be checked out of the main @@ -262,7 +266,7 @@ Subversion, or SVN, is one of several revision control packages. It was selected for GNU projects because it's free (speech), free (beer), and very high - quality. The Subversion + quality. The Subversion home page has a better description.

The “anonymous client checkout” feature of SVN is @@ -270,21 +274,21 @@ the latest libstdc++ sources.

For more information - see SVN + see SVN details. -

3.3.

How do I know if it works? -

+

3.3.

How do I know if it works? +

Libstdc++ comes with its own validation testsuite, which includes conformance testing, regression testing, ABI testing, and performance testing. Please consult the - testing + testing documentation for more details.

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! -

3.4.

How do I insure that the dynamically linked library will be found? -

+

3.4.

How do I insure that the dynamically linked library will be found? +

Depending on your platform and library version, the error message might be similar to one of the following: 

@@ -317,9 +321,9 @@
     

     Using LD_LIBRARY_PATH is not always the best solution, Finding Dynamic or Shared
     Libraries in the manual gives some alternatives.
-

3.5.

+

3.5.

What's libsupc++? -

+

If the only functions from libstdc++.a which you need are language support functions (those listed in clause 18 of the @@ -334,9 +338,9 @@ using anything from the rest of the library, such as IOStreams or vectors, then you'll still need pieces from libstdc++.a. -

3.6.

+

3.6.

This library is HUGE! -

+

Usually the size of libraries on disk isn't noticeable. When a link editor (or simply “linker”) pulls things from a static archive library, only the necessary object files are copied @@ -381,9 +385,9 @@ Recent GNU/Linux glibc required?

4.8. Can't use wchar_t/wstring on FreeBSD -

4.1.

+

4.1.

Can libstdc++ be used with non-GNU compilers? -

+

Perhaps.

Since the goal of ISO Standardization is for all C++ @@ -401,9 +405,9 @@ been known to work with versions of the EDG C++ compiler, and vendor-specific proprietary C++ compilers such as the Intel ICC C++ compiler. -

4.2.

+

4.2.

No 'long long' type on Solaris? -

+

By default we try to support the C99 long long type. This requires that certain functions from your C library be present.

@@ -413,9 +417,9 @@ commonly reported platform affected was Solaris.

This has been fixed for libstdc++ releases greater than 3.0.3. -

4.3.

+

4.3.

_XOPEN_SOURCE and _GNU_SOURCE are always defined? -

On Solaris, g++ (but not gcc) always defines the preprocessor +

On Solaris, g++ (but not gcc) always defines the preprocessor macro _XOPEN_SOURCE. On GNU/Linux, the same happens with _GNU_SOURCE. (This is not an exhaustive list; other macros and other platforms are also affected.) @@ -439,18 +443,18 @@ g++ -E -dM - < /dev/null" to display a list of predefined macros for any particular installation.

This has been discussed on the mailing lists - quite a bit. + quite a bit.

This method is something of a wart. We'd like to find a cleaner solution, but nobody yet has contributed the time. -

4.4.

+

4.4.

Mac OS X ctype.h is broken! How can I fix it? -

This is a long-standing bug in the OS X support. Fortunately, +

This is a long-standing bug in the OS X support. Fortunately, the patch is quite simple, and well-known. - Here's a + Here's a link to the solution. -

4.5.

+

4.5.

Threading is broken on i386? -

+

Support for atomic integer operations is/was broken on i386 platforms. The assembly code accidentally used opcodes that are only available on the i486 and later. So if you configured GCC @@ -458,9 +462,9 @@ on an i686, then you would encounter no problems. Only when actually running the code on a i386 will the problem appear.

This is fixed in 3.2.2. -

4.6.

+

4.6.

MIPS atomic operations -

+

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 the generic implementation instead. You can also @@ -468,9 +472,9 @@

The mips*-*-linux* port continues to use the MIPS II routines, and more work in this area is expected. -

4.7.

+

4.7.

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 5.0.1) and later uses localization and formatting code from the system C library (glibc) version 2.2.5 which contains necessary bugfixes. Most GNU/Linux distros make more recent versions available now. @@ -479,9 +483,9 @@

The guideline is simple: the more recent the C++ library, the more recent the C library. (This is also documented in the main GCC installation instructions.) -

4.8.

+

4.8.

Can't use wchar_t/wstring on FreeBSD -

+

Older versions of FreeBSD's C library do not have sufficient support for wide character functions, and as a result the libstdc++ configury decides that wchar_t support should be @@ -498,9 +502,9 @@ Bugs in the ISO C++ language or library specification

5.3. Bugs in the compiler (gcc/g++) and not libstdc++ -

5.1.

+

5.1.

What works already? -

+

Short answer: Pretty much everything works except for some corner cases. Support for localization in locale may be incomplete on non-GNU @@ -512,24 +516,24 @@ C++98, TR1, and C++11. -

5.2.

+

5.2.

Bugs in the ISO C++ language or library specification -

+

Unfortunately, there are some.

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 public list of the library defects is occasionally - published on the WG21 + published on the WG21 website. Some of these issues have resulted in code changes in libstdc++.

If you think you've discovered a new bug that is not listed, please post a message describing your problem to the author of the library issues list or the Usenet group comp.lang.c++.moderated. -

5.3.

+

5.3.

Bugs in the compiler (gcc/g++) and not libstdc++ -

+

On occasion, the compiler is wrong. Please be advised that this happens much less often than one would think, and avoid jumping to conclusions. @@ -540,7 +544,7 @@ these lists with terms describing your issue.

Before reporting a bug, please examine the - bugs database with the + bugs database with the category set to “g++”.

6.1. Reopening a stream fails @@ -562,19 +566,19 @@ list::size() is O(n)!
6.9. Aw, that's easy to fix! -

6.1.

+

6.1.

Reopening a stream fails -

+

One of the most-reported non-bug reports. Executing a sequence like: -


-    #include <fstream>
-    ...
-    std::fstream  fs(“a_file”);
-    // .
-    // . do things with fs...
-    // .
-    fs.close();
-    fs.open(“a_new_file”);
+


+    #include <fstream>
+    ...
+    std::fstream  fs(“a_file”);
+    // .
+    // . do things with fs...
+    // .
+    fs.close();
+    fs.open(“a_new_file”);
    

All operations on the re-opened fs will fail, or at least act very strangely. Yes, they often will, especially if @@ -589,9 +593,9 @@ Update: for GCC 4.0 we implemented the resolution of DR #409 and open() now calls clear() on success! -

6.2.

+

6.2.

-Weffc++ complains too much -

+

Many warnings are emitted when -Weffc++ is used. Making libstdc++ -Weffc++-clean is not a goal of the project, for a few reasons. Mainly, that option tries to enforce @@ -601,21 +605,21 @@ We do, however, try to have libstdc++ sources as clean as possible. If you see some simple changes that pacify -Weffc++ without other drawbacks, send us a patch. -

6.3.

+

6.3.

Ambiguous overloads after including an old-style header -

+

Another problem is the rel_ops namespace and the template comparison operator functions contained therein. If they become visible in the same namespace as other comparison functions (e.g., “using” them and the <iterator> header), then you will suddenly be faced with huge numbers of ambiguity errors. This was discussed on the -v3 list; Nathan Myers - sums + sums things up here. The collisions with vector/string iterator types have been fixed for 3.1. -

6.4.

+

6.4.

The g++-3 headers are not ours -

+

If you are using headers in ${prefix}/include/g++-3, or if the installed library's name looks like libstdc++-2.10.a or @@ -629,10 +633,10 @@ 'v'?). Starting with version 3.2 the headers are installed in ${prefix}/include/c++/${version} as this prevents headers from previous versions being found by mistake. -

6.5.

+

6.5.

Errors about *Concept and constraints in the STL -

+

If you see compilation errors containing messages about foo Concept and something to do with a constraints member function, then most @@ -646,31 +650,31 @@ checks, is available in the Diagnostics. chapter of the manual. -

6.6.

+

6.6.

Program crashes when using library code in a dynamically-loaded library -

+

If you are using the C++ library across dynamically-loaded objects, make certain that you are passing the correct options when compiling and linking: -


-    // compile your library components
-    g++ -fPIC -c a.cc
-    g++ -fPIC -c b.cc
-    ...
-    g++ -fPIC -c z.cc
-
-    // create your library
-    g++ -fPIC -shared -rdynamic -o libfoo.so a.o b.o ... z.o
-
-    // link the executable
-    g++ -fPIC -rdynamic -o foo ... -L. -lfoo -ldl
-    

6.7.

+


+    // compile your library components
+    g++ -fPIC -c a.cc
+    g++ -fPIC -c b.cc
+    ...
+    g++ -fPIC -c z.cc
+
+    // create your library
+    g++ -fPIC -shared -rdynamic -o libfoo.so a.o b.o ... z.o
+
+    // link the executable
+    g++ -fPIC -rdynamic -o foo ... -L. -lfoo -ldl
+    

6.7.

“Memory leaks” in containers -

+

A few people have reported that the standard containers appear to leak memory when tested with memory checkers such as - valgrind. + valgrind. Under some configurations the library's allocators keep 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 never @@ -678,18 +682,18 @@ want to test the library for memory leaks please read Tips for memory leak hunting first. -

6.8.

+

6.8.

list::size() is O(n)! -

+

See the Containers chapter. -

6.9.

+

6.9.

Aw, that's easy to fix! -

+

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 submitting + on submitting patches that covers the procedure, but for libstdc++ you should also send the patch to our mailing list in addition to the GCC patches mailing list. The libstdc++ @@ -717,9 +721,9 @@ What's an ABI and why is it so messy?

7.8. How do I make std::vector<T>::capacity() == std::vector<T>::size? -

7.1.

+

7.1.

string::iterator is not char*; vector<T>::iterator is not T* -

+

If you have code that depends on container<T> iterators being implemented as pointer-to-T, your code is broken. It's considered a feature, not a bug, that libstdc++ points this out. @@ -736,9 +740,9 @@ certain expressions to &*i. Future revisions of the Standard are expected to bless this usage for vector<> (but not for basic_string<>). -

7.2.

+

7.2.

What's next after libstdc++? -

+

Hopefully, not much. The goal of libstdc++ is to produce a fully-compliant, fully-portable Standard Library. After that, we're mostly done: there won't be any @@ -747,12 +751,12 @@ There is an effort underway to add significant extensions to the standard library specification. The latest version of this effort is described in - + The C++ Library Technical Report 1. -

7.3.

+

7.3.

What about the STL from SGI? -

- The STL from SGI, +

+ The STL from SGI, version 3.3, was the final merge of the STL codebase. The code in libstdc++ contains many fixes and changes, and the SGI code is no longer under active @@ -772,24 +776,24 @@

The FAQ for SGI's STL (one jump off of their main page) is still recommended reading. -

7.4.

+

7.4.

Extensions and Backward Compatibility -

+

See the link on backwards compatibility and link on evolution. -

7.5.

+

7.5.

Does libstdc++ support TR1? -

+

Yes.

The C++ Standard Library Technical Report adds many new features to the library. The latest version of this effort is described in - + Technical Report 1.

The implementation status of TR1 in libstdc++ can be tracked on the TR1 status page. -

7.6.

How do I get a copy of the ISO C++ Standard? -

+

7.6.

How do I get a copy of the ISO C++ Standard? +

Copies of the full ISO 14882 standard are available on line via the ISO mirror site for committee members. Non-members, or those who have not paid for the privilege of sitting on the committee @@ -797,19 +801,19 @@ get a copy of the standard from their respective national standards organization. In the USA, this national standards organization is ANSI and their website is - right here. (And if + right here. (And if you've already registered with them, clicking this link will take you to directly to the place where you can - buy the standard on-line. + buy the standard on-line.

Who is your country's member body? Visit the - ISO homepage and find out! + ISO homepage and find out!

The 2003 version of the standard (the 1998 version plus TC1) is available in print, ISBN 0-470-84674-7. -

7.7.

+

7.7.

What's an ABI and why is it so messy? -

+

ABI stands for “Application Binary Interface”. Conventionally, it refers to a great mass of details about how arguments are arranged on the call @@ -855,17 +859,17 @@ so they may later be changed. Deciding which, and implementing the decisions, must happen before you can reasonably document a candidate C++ ABI that encompasses the standard library. -

7.8.

+

7.8.

How do I make std::vector<T>::capacity() == std::vector<T>::size? -

+

The standard idiom for deallocating a vector<T>'s unused memory is to create a temporary copy of the vector and swap their contents, e.g. for vector<T> v -


-     std::vector<T>(v).swap(v);
+


+     std::vector<T>(v).swap(v);
    

The copy will take O(n) time and the swap is constant time.

See Shrink-to-fit strings for a similar solution for strings. -

Prev Up 
 Home 
+

Prev Up 
 Home 
diff --git a/libstdc++-v3/doc/html/index.html b/libstdc++-v3/doc/html/index.html index c4a5cf56ab4..dec3001b5ed 100644 --- a/libstdc++-v3/doc/html/index.html +++ b/libstdc++-v3/doc/html/index.html @@ -1,8 +1,12 @@ - - -The GNU C++ Library
The GNU C++ Library
   Next

Short Contents

+The GNU C++ Library

The GNU C++ Library
   Next

The GNU C++ Library

Short Contents

Copyright 2008, 2009, 2011 - FSF + FSF

Permission is granted to copy, distribute and/or modify this @@ -14,14 +18,14 @@ This is the top level of the libstdc++ documentation set. The documentation is divided into the following three sections.

-

Table of Contents

The GNU C++ Library Manual
I. +

Table of Contents

The GNU C++ Library Manual
I. Introduction
1. Status
Implementation Status
C++ 1998/2003
Implementation Status
Implementation Specific Behavior
C++ 2011
Implementation Specific Behavior
C++ TR1
Implementation Specific Behavior
C++ TR 24733
License
The Code: GPL
The Documentation: GPL, FDL
Bugs
Implementation Bugs
Standard Bugs
2. Setup
Prerequisites
Configure
Make
3. Using
Command Options
Headers
Header Files
Mixing Headers
The C Headers and namespace std
Precompiled Headers
Macros
Namespaces
Available Namespaces
namespace std
Using Namespace Composition
Linking
Almost Nothing
Finding Dynamic or Shared Libraries
Concurrency
Prerequisites
Thread Safety
Atomics
IO
Structure
Defaults
Future
Alternatives
Containers
Exceptions
Exception Safety
Exception Neutrality
Doing without
Compatibility
With C
With POSIX thread cancellation
Debugging Support
Using g++
Debug Versions of Library Binary Files
Memory Leak Hunting
Data Race Hunting
Using gdb
Tracking uncaught exceptions
Debug Mode
Compile Time Checking
Profile-based Performance Analysis
II. @@ -35,13 +39,13 @@
Exceptions
API Reference
Adding Data to exception
Concept Checking
6. Utilities -
Functors
Pairs
Memory
Allocators
Requirements
Design Issues
Implementation
Interface Design
Selecting Default Allocation Policy
Disabling Memory Caching
Using a Specific Allocator
Custom Allocators
Extension Allocators
auto_ptr
Limitations
Use in Containers
shared_ptr
Requirements
Design Issues
Implementation
Class Hierarchy
Thread Safety
Selecting Lock Policy
Related functions and classes
Use
Examples
Unresolved Issues
Acknowledgments
Traits
7. +
Functors
Pairs
Memory
Allocators
Requirements
Design Issues
Implementation
Interface Design
Selecting Default Allocation Policy
Disabling Memory Caching
Using a Specific Allocator
Custom Allocators
Extension Allocators
auto_ptr
Limitations
Use in Containers
shared_ptr
Requirements
Design Issues
Implementation
Class Hierarchy
Thread Safety
Selecting Lock Policy
Related functions and classes
Use
Examples
Unresolved Issues
Acknowledgments
Traits
7. Strings
String Classes
Simple Transformations
Case Sensitivity
Arbitrary Character Types
Tokenizing
Shrink to Fit
CString (MFC)
8. Localization -
Locales
locale
Requirements
Design
Implementation
Interacting with "C" locales
Future
Facets
ctype
Implementation
Specializations
Future
codecvt
Requirements
Design
wchar_t Size
Support for Unicode
Other Issues
Implementation
Use
Future
messages
Requirements
Design
Implementation
Models
The GNU Model
Use
Future
9. +
Locales
locale
Requirements
Design
Implementation
Interacting with "C" locales
Future
Facets
ctype
Implementation
Specializations
Future
codecvt
Requirements
Design
wchar_t Size
Support for Unicode
Other Issues
Implementation
Use
Future
messages
Requirements
Design
Implementation
Models
The GNU Model
Use
Future
9. Containers
Sequences
list
list::size() is O(n)
vector
Space Overhead Management
Associative
Insertion Hints
bitset
Size Variable
Type String
Interacting with C
Containers vs. Arrays
10. @@ -65,7 +69,7 @@
API Reference
III. Extensions -
16. Compile Time Checks
17. Debug Mode
Intro
Semantics
Using
Using the Debug Mode
Using a Specific Debug Container
Design
Goals
Methods
The Wrapper Model
Safe Iterators
Safe Sequences (Containers)
Precondition Checking
Release- and debug-mode coexistence
Compile-time coexistence of release- and debug-mode components
Link- and run-time coexistence of release- and +
16. Compile Time Checks
17. Debug Mode
Intro
Semantics
Using
Using the Debug Mode
Using a Specific Debug Container
Design
Goals
Methods
The Wrapper Model
Safe Iterators
Safe Sequences (Containers)
Precondition Checking
Release- and debug-mode coexistence
Compile-time coexistence of release- and debug-mode components
Link- and run-time coexistence of release- and debug-mode components
Alternatives for Coexistence
Other Implementations
18. Parallel Mode
Intro
Semantics
Using
Prerequisite Compiler Flags
Using Parallel Mode
Using Specific Parallel Components
Design
Interface Basics
Configuration and Tuning
Setting up the OpenMP Environment
Compile Time Switches
Run Time Settings and Defaults
Implementation Namespaces
Testing
Bibliography
19. Profile Mode
Intro
Using the Profile Mode
Tuning the Profile Mode
Design
Wrapper Model
Instrumentation
Run Time Behavior
Analysis and Diagnostics
Cost Model
Reports
Testing
Extensions for Custom Containers
Empirical Cost Model
Implementation Issues
Stack Traces
Symbolization of Instruction Addresses
Concurrency
Using the Standard Library in the Instrumentation Implementation
Malloc Hooks
Construction and Destruction of Global Objects
Developer Information
Big Picture
How To Add A Diagnostic
Diagnostics
Diagnostic Template
Containers
Hashtable Too Small
Hashtable Too Large
Inefficient Hash
Vector Too Small
Vector Too Large
Vector to Hashtable
Hashtable to Vector
Vector to List
List to Vector
List to Forward List (Slist)
Ordered to Unordered Associative Container
Algorithms
Sort Algorithm Performance
Data Locality
Need Software Prefetch
Linked Structure Locality
Multithreaded Data Access
Data Dependence Violations at Container Level
False Sharing
Statistics
Bibliography
20. The mt_allocator
Intro
Design Issues
Overview
Implementation
Tunable Parameters
Initialization
Deallocation Notes
Single Thread Example
Multiple Thread Example
21. The bitmap_allocator
Design
Implementation
Free List Store
Super Block
Super Block Data Layout
Maximum Wasted Percentage
allocate
deallocate
Questions
1
2
3
Locality
Overhead and Grow Policy
22. Policy-Based Data Structures
Intro
Performance Issues
Associative
Priority Que
Goals
Associative
Policy Choices
Underlying Data Structures
Iterators
Functional
Priority Queues
Policy Choices
Underlying Data Structures
Binary Heaps
Using
Prerequisites
Organization
Tutorial
Basic Use
Configuring via Template Parameters
@@ -165,4 +169,4 @@ Support for C++11 dialect.
D. GNU General Public License version 3 -
E. GNU Free Documentation License
The GNU C++ Library API Reference
Frequently Asked Questions
   Next
   The GNU C++ Library Manual
+
E. GNU Free Documentation License
The GNU C++ Library API Reference
Frequently Asked Questions
   Next
   The GNU C++ Library Manual
diff --git a/libstdc++-v3/doc/html/manual/abi.html b/libstdc++-v3/doc/html/manual/abi.html index bc091d0ac11..b1ec7a46bde 100644 --- a/libstdc++-v3/doc/html/manual/abi.html +++ b/libstdc++-v3/doc/html/manual/abi.html @@ -1,10 +1,30 @@ - - -ABI Policy and Guidelines
ABI Policy and Guidelines
Prev Appendix B.  +ABI Policy and Guidelines
ABI Policy and Guidelines
Prev Appendix B.  Porting and Maintenance - Next

-

+

 Next

ABI Policy and Guidelines

+

The C++ Interface

C++ applications often depend on specific language support routines, say for throwing exceptions, or catching exceptions, and perhaps also depend on features in the C++ Standard Library. @@ -21,7 +41,7 @@ virtual functions, etc. These details are defined as the compiler Application Binary Interface, or ABI. The GNU C++ compiler uses an industry-standard C++ ABI starting with version 3. Details can be - found in the ABI + found in the ABI specification.

The GNU C++ compiler, g++, has a compiler command line option to @@ -30,7 +50,7 @@ g++ command line options may change the ABI as a side-effect of use. Such flags include -fpack-struct and -fno-exceptions, but include others: see the complete - list in the GCC manual under the heading Options + list in the GCC manual under the heading Options for Code Generation Conventions.

The configure options used when building a specific libstdc++ @@ -58,10 +78,10 @@ given compiler ABI. In a nutshell: To use a specific version of the C++ ABI, one must use a corresponding GNU C++ toolchain (i.e., g++ and libstdc++) that implements the C++ ABI in question. -

The C++ interface has evolved throughout the history of the GNU +

Versioning

The C++ interface has evolved throughout the history of the GNU C++ toolchain. With each release, various details have been changed so as to give distinct versions to the C++ interface. -

Extending existing, stable ABIs. Versioning gives subsequent +

Goals

Extending existing, stable ABIs. Versioning gives subsequent releases of library binaries the ability to add new symbols and add functionality, all the while retaining compatibility with the previous releases in the series. Thus, program binaries linked with the initial @@ -75,7 +95,7 @@ binary in a release series (with additional symbols added), substitute in the initial release of the library binary, and remain link compatible.

Allows multiple, incompatible ABIs to coexist at the same time. -

+

History

How can this complexity be managed? What does C++ versioning mean? Because library and compiler changes often make binaries compiled with one version of the GNU tools incompatible with binaries @@ -84,12 +104,12 @@ compatible. easier.

The following techniques are used: -

  1. Release versioning on the libgcc_s.so binary.

    This is implemented via file names and the ELF +

    1. Release versioning on the libgcc_s.so binary.

      This is implemented via file names and the ELF DT_SONAME mechanism (at least on ELF systems). It is versioned as follows: -

      • GCC 3.x: libgcc_s.so.1

      • GCC 4.x: libgcc_s.so.1

      For m68k-linux the versions differ as follows:

      • GCC 3.4, GCC 4.x: libgcc_s.so.1 +

        • GCC 3.x: libgcc_s.so.1

        • GCC 4.x: libgcc_s.so.1

        For m68k-linux the versions differ as follows:

        • GCC 3.4, GCC 4.x: libgcc_s.so.1 when configuring --with-sjlj-exceptions, or - libgcc_s.so.2

        For hppa-linux the versions differ as follows:

        • GCC 3.4, GCC 4.[0-1]: either libgcc_s.so.1 + libgcc_s.so.2

        For hppa-linux the versions differ as follows:

        • GCC 3.4, GCC 4.[0-1]: either libgcc_s.so.1 when configuring --with-sjlj-exceptions, or libgcc_s.so.2

        • GCC 4.[2-7]: either libgcc_s.so.3 when configuring --with-sjlj-exceptions) or libgcc_s.so.4 @@ -97,7 +117,7 @@ compatible. definitions, where the version definition is the maximum for a particular release. Labels are cumulative. If a particular release is not listed, it has the same version labels as the preceding - release.

          This corresponds to the mapfile: gcc/libgcc-std.ver

          • GCC 3.0.0: GCC_3.0

          • GCC 3.3.0: GCC_3.3

          • GCC 3.3.1: GCC_3.3.1

          • GCC 3.3.2: GCC_3.3.2

          • GCC 3.3.4: GCC_3.3.4

          • GCC 3.4.0: GCC_3.4

          • GCC 3.4.2: GCC_3.4.2

          • GCC 3.4.4: GCC_3.4.4

          • GCC 4.0.0: GCC_4.0.0

          • GCC 4.1.0: GCC_4.1.0

          • GCC 4.2.0: GCC_4.2.0

          • GCC 4.3.0: GCC_4.3.0

          • GCC 4.4.0: GCC_4.4.0

          • GCC 4.5.0: GCC_4.5.0

          • GCC 4.6.0: GCC_4.6.0

          • GCC 4.7.0: GCC_4.7.0

        • + release.

          This corresponds to the mapfile: gcc/libgcc-std.ver

          • GCC 3.0.0: GCC_3.0

          • GCC 3.3.0: GCC_3.3

          • GCC 3.3.1: GCC_3.3.1

          • GCC 3.3.2: GCC_3.3.2

          • GCC 3.3.4: GCC_3.3.4

          • GCC 3.4.0: GCC_3.4

          • GCC 3.4.2: GCC_3.4.2

          • GCC 3.4.4: GCC_3.4.4

          • GCC 4.0.0: GCC_4.0.0

          • GCC 4.1.0: GCC_4.1.0

          • GCC 4.2.0: GCC_4.2.0

          • GCC 4.3.0: GCC_4.3.0

          • GCC 4.4.0: GCC_4.4.0

          • GCC 4.5.0: GCC_4.5.0

          • GCC 4.6.0: GCC_4.6.0

          • GCC 4.7.0: GCC_4.7.0

        • Release versioning on the libstdc++.so binary, implemented in the same way as the libgcc_s.so binary above. Listed is the filename: DT_SONAME can be deduced from @@ -112,13 +132,13 @@ compatible. has the same filename and DT_SONAME as the preceding release.

          It is versioned as follows: -

          • GCC 3.0.0: libstdc++.so.3.0.0

          • GCC 3.0.1: libstdc++.so.3.0.1

          • GCC 3.0.2: libstdc++.so.3.0.2

          • GCC 3.0.3: libstdc++.so.3.0.2 (See Note 1)

          • GCC 3.0.4: libstdc++.so.3.0.4

          • GCC 3.1.0: libstdc++.so.4.0.0 (Incompatible with previous)

          • GCC 3.1.1: libstdc++.so.4.0.1

          • GCC 3.2.0: libstdc++.so.5.0.0 (Incompatible with previous)

          • GCC 3.2.1: libstdc++.so.5.0.1

          • GCC 3.2.2: libstdc++.so.5.0.2

          • GCC 3.2.3: libstdc++.so.5.0.3 (See Note 2)

          • GCC 3.3.0: libstdc++.so.5.0.4

          • GCC 3.3.1: libstdc++.so.5.0.5

          • GCC 3.4.0: libstdc++.so.6.0.0 (Incompatible with previous)

          • GCC 3.4.1: libstdc++.so.6.0.1

          • GCC 3.4.2: libstdc++.so.6.0.2

          • GCC 3.4.3: libstdc++.so.6.0.3

          • GCC 4.0.0: libstdc++.so.6.0.4

          • GCC 4.0.1: libstdc++.so.6.0.5

          • GCC 4.0.2: libstdc++.so.6.0.6

          • GCC 4.0.3: libstdc++.so.6.0.7

          • GCC 4.1.0: libstdc++.so.6.0.7

          • GCC 4.1.1: libstdc++.so.6.0.8

          • GCC 4.2.0: libstdc++.so.6.0.9

          • GCC 4.2.1: libstdc++.so.6.0.9 (See Note 3)

          • GCC 4.2.2: libstdc++.so.6.0.9

          • GCC 4.3.0: libstdc++.so.6.0.10

          • GCC 4.4.0: libstdc++.so.6.0.11

          • GCC 4.4.1: libstdc++.so.6.0.12

          • GCC 4.4.2: libstdc++.so.6.0.13

          • GCC 4.5.0: libstdc++.so.6.0.14

          • GCC 4.6.0: libstdc++.so.6.0.15

          • GCC 4.6.1: libstdc++.so.6.0.16

          +

          • GCC 3.0.0: libstdc++.so.3.0.0

          • GCC 3.0.1: libstdc++.so.3.0.1

          • GCC 3.0.2: libstdc++.so.3.0.2

          • GCC 3.0.3: libstdc++.so.3.0.2 (See Note 1)

          • GCC 3.0.4: libstdc++.so.3.0.4

          • GCC 3.1.0: libstdc++.so.4.0.0 (Incompatible with previous)

          • GCC 3.1.1: libstdc++.so.4.0.1

          • GCC 3.2.0: libstdc++.so.5.0.0 (Incompatible with previous)

          • GCC 3.2.1: libstdc++.so.5.0.1

          • GCC 3.2.2: libstdc++.so.5.0.2

          • GCC 3.2.3: libstdc++.so.5.0.3 (See Note 2)

          • GCC 3.3.0: libstdc++.so.5.0.4

          • GCC 3.3.1: libstdc++.so.5.0.5

          • GCC 3.4.0: libstdc++.so.6.0.0 (Incompatible with previous)

          • GCC 3.4.1: libstdc++.so.6.0.1

          • GCC 3.4.2: libstdc++.so.6.0.2

          • GCC 3.4.3: libstdc++.so.6.0.3

          • GCC 4.0.0: libstdc++.so.6.0.4

          • GCC 4.0.1: libstdc++.so.6.0.5

          • GCC 4.0.2: libstdc++.so.6.0.6

          • GCC 4.0.3: libstdc++.so.6.0.7

          • GCC 4.1.0: libstdc++.so.6.0.7

          • GCC 4.1.1: libstdc++.so.6.0.8

          • GCC 4.2.0: libstdc++.so.6.0.9

          • GCC 4.2.1: libstdc++.so.6.0.9 (See Note 3)

          • GCC 4.2.2: libstdc++.so.6.0.9

          • GCC 4.3.0: libstdc++.so.6.0.10

          • GCC 4.4.0: libstdc++.so.6.0.11

          • GCC 4.4.1: libstdc++.so.6.0.12

          • GCC 4.4.2: libstdc++.so.6.0.13

          • GCC 4.5.0: libstdc++.so.6.0.14

          • GCC 4.6.0: libstdc++.so.6.0.15

          • GCC 4.6.1: libstdc++.so.6.0.16

          Note 1: Error should be libstdc++.so.3.0.3.

          Note 2: Not strictly required.

          Note 3: This release (but not previous or subsequent) has one - known incompatibility, see 33678 + known incompatibility, see 33678 in the GCC bug database.

        • Symbol versioning on the libstdc++.so binary.

          mapfile: libstdc++-v3/config/abi/pre/gnu.ver

          It is versioned with the following labels and version definitions, where the version definition is the maximum for a @@ -130,7 +150,7 @@ compatible. GLIBCPP_3.2 for symbols that were introduced in the GCC 3.2.0 release.) If a particular release is not listed, it has the same version labels as the preceding release. -

          • GCC 3.0.0: (Error, not versioned)

          • GCC 3.0.1: (Error, not versioned)

          • GCC 3.0.2: (Error, not versioned)

          • GCC 3.0.3: (Error, not versioned)

          • GCC 3.0.4: (Error, not versioned)

          • GCC 3.1.0: GLIBCPP_3.1, CXXABI_1

          • GCC 3.1.1: GLIBCPP_3.1, CXXABI_1

          • GCC 3.2.0: GLIBCPP_3.2, CXXABI_1.2

          • GCC 3.2.1: GLIBCPP_3.2.1, CXXABI_1.2

          • GCC 3.2.2: GLIBCPP_3.2.2, CXXABI_1.2

          • GCC 3.2.3: GLIBCPP_3.2.2, CXXABI_1.2

          • GCC 3.3.0: GLIBCPP_3.2.2, CXXABI_1.2.1

          • GCC 3.3.1: GLIBCPP_3.2.3, CXXABI_1.2.1

          • GCC 3.3.2: GLIBCPP_3.2.3, CXXABI_1.2.1

          • GCC 3.3.3: GLIBCPP_3.2.3, CXXABI_1.2.1

          • GCC 3.4.0: GLIBCXX_3.4, CXXABI_1.3

          • GCC 3.4.1: GLIBCXX_3.4.1, CXXABI_1.3

          • GCC 3.4.2: GLIBCXX_3.4.2

          • GCC 3.4.3: GLIBCXX_3.4.3

          • GCC 4.0.0: GLIBCXX_3.4.4, CXXABI_1.3.1

          • GCC 4.0.1: GLIBCXX_3.4.5

          • GCC 4.0.2: GLIBCXX_3.4.6

          • GCC 4.0.3: GLIBCXX_3.4.7

          • GCC 4.1.1: GLIBCXX_3.4.8

          • GCC 4.2.0: GLIBCXX_3.4.9

          • GCC 4.3.0: GLIBCXX_3.4.10, CXXABI_1.3.2

          • GCC 4.4.0: GLIBCXX_3.4.11, CXXABI_1.3.3

          • GCC 4.4.1: GLIBCXX_3.4.12, CXXABI_1.3.3

          • GCC 4.4.2: GLIBCXX_3.4.13, CXXABI_1.3.3

          • GCC 4.5.0: GLIBCXX_3.4.14, CXXABI_1.3.4

          • GCC 4.6.0: GLIBCXX_3.4.15, CXXABI_1.3.5

          • GCC 4.6.1: GLIBCXX_3.4.16, CXXABI_1.3.5

        • Incremental bumping of a compiler pre-defined macro, +

          • GCC 3.0.0: (Error, not versioned)

          • GCC 3.0.1: (Error, not versioned)

          • GCC 3.0.2: (Error, not versioned)

          • GCC 3.0.3: (Error, not versioned)

          • GCC 3.0.4: (Error, not versioned)

          • GCC 3.1.0: GLIBCPP_3.1, CXXABI_1

          • GCC 3.1.1: GLIBCPP_3.1, CXXABI_1

          • GCC 3.2.0: GLIBCPP_3.2, CXXABI_1.2

          • GCC 3.2.1: GLIBCPP_3.2.1, CXXABI_1.2

          • GCC 3.2.2: GLIBCPP_3.2.2, CXXABI_1.2

          • GCC 3.2.3: GLIBCPP_3.2.2, CXXABI_1.2

          • GCC 3.3.0: GLIBCPP_3.2.2, CXXABI_1.2.1

          • GCC 3.3.1: GLIBCPP_3.2.3, CXXABI_1.2.1

          • GCC 3.3.2: GLIBCPP_3.2.3, CXXABI_1.2.1

          • GCC 3.3.3: GLIBCPP_3.2.3, CXXABI_1.2.1

          • GCC 3.4.0: GLIBCXX_3.4, CXXABI_1.3

          • GCC 3.4.1: GLIBCXX_3.4.1, CXXABI_1.3

          • GCC 3.4.2: GLIBCXX_3.4.2

          • GCC 3.4.3: GLIBCXX_3.4.3

          • GCC 4.0.0: GLIBCXX_3.4.4, CXXABI_1.3.1

          • GCC 4.0.1: GLIBCXX_3.4.5

          • GCC 4.0.2: GLIBCXX_3.4.6

          • GCC 4.0.3: GLIBCXX_3.4.7

          • GCC 4.1.1: GLIBCXX_3.4.8

          • GCC 4.2.0: GLIBCXX_3.4.9

          • GCC 4.3.0: GLIBCXX_3.4.10, CXXABI_1.3.2

          • GCC 4.4.0: GLIBCXX_3.4.11, CXXABI_1.3.3

          • GCC 4.4.1: GLIBCXX_3.4.12, CXXABI_1.3.3

          • GCC 4.4.2: GLIBCXX_3.4.13, CXXABI_1.3.3

          • GCC 4.5.0: GLIBCXX_3.4.14, CXXABI_1.3.4

          • GCC 4.6.0: GLIBCXX_3.4.15, CXXABI_1.3.5

          • GCC 4.6.1: GLIBCXX_3.4.16, CXXABI_1.3.5

        • Incremental bumping of a compiler pre-defined macro, __GXX_ABI_VERSION. This macro is defined as the version of the compiler v3 ABI, with g++ 3.0 being version 100. This macro will be automatically defined whenever g++ is used (the curious can @@ -142,11 +162,11 @@ compatible. '-fabi-version' command line option.

          It is versioned as follows, where 'n' is given by '-fabi-version=n': -

          • GCC 3.0: 100

          • GCC 3.1: 100 (Error, should be 101)

          • GCC 3.2: 102

          • GCC 3.3: 102

          • GCC 3.4, GCC 4.x: 102 (when n=1)

          • GCC 3.4, GCC 4.x: 1000 + n (when n>1)

          • GCC 3.4, GCC 4.x: 999999 (when n=0)

        • Changes to the default compiler option for +

          • GCC 3.0: 100

          • GCC 3.1: 100 (Error, should be 101)

          • GCC 3.2: 102

          • GCC 3.3: 102

          • GCC 3.4, GCC 4.x: 102 (when n=1)

          • GCC 3.4, GCC 4.x: 1000 + n (when n>1)

          • GCC 3.4, GCC 4.x: 999999 (when n=0)

        • Changes to the default compiler option for -fabi-version.

          It is versioned as follows: -

          • GCC 3.0: (Error, not versioned)

          • GCC 3.1: (Error, not versioned)

          • GCC 3.2: -fabi-version=1

          • GCC 3.3: -fabi-version=1

          • GCC 3.4, GCC 4.x: -fabi-version=2 (Incompatible with previous)

        • Incremental bumping of a library pre-defined macro. For releases +

          • GCC 3.0: (Error, not versioned)

          • GCC 3.1: (Error, not versioned)

          • GCC 3.2: -fabi-version=1

          • GCC 3.3: -fabi-version=1

          • GCC 3.4, GCC 4.x: -fabi-version=2 (Incompatible with previous)

        • Incremental bumping of a library pre-defined macro. For releases before 3.4.0, the macro is __GLIBCPP__. For later releases, it's __GLIBCXX__. (The libstdc++ project generously changed from CPP to CXX throughout its source to allow the "C" pre-processor the CPP @@ -159,7 +179,7 @@ compatible. the same value as gcc/DATESTAMP.)

          It is versioned as follows: -

          • GCC 3.0.0: 20010615

          • GCC 3.0.1: 20010819

          • GCC 3.0.2: 20011023

          • GCC 3.0.3: 20011220

          • GCC 3.0.4: 20020220

          • GCC 3.1.0: 20020514

          • GCC 3.1.1: 20020725

          • GCC 3.2.0: 20020814

          • GCC 3.2.1: 20021119

          • GCC 3.2.2: 20030205

          • GCC 3.2.3: 20030422

          • GCC 3.3.0: 20030513

          • GCC 3.3.1: 20030804

          • GCC 3.3.2: 20031016

          • GCC 3.3.3: 20040214

          • GCC 3.4.0: 20040419

          • GCC 3.4.1: 20040701

          • GCC 3.4.2: 20040906

          • GCC 3.4.3: 20041105

          • GCC 3.4.4: 20050519

          • GCC 3.4.5: 20051201

          • GCC 3.4.6: 20060306

          • GCC 4.0.0: 20050421

          • GCC 4.0.1: 20050707

          • GCC 4.0.2: 20050921

          • GCC 4.0.3: 20060309

          • GCC 4.1.0: 20060228

          • GCC 4.1.1: 20060524

          • GCC 4.1.2: 20070214

          • GCC 4.2.0: 20070514

          • GCC 4.2.1: 20070719

          • GCC 4.2.2: 20071007

          • GCC 4.2.3: 20080201

          • GCC 4.2.4: 20080519

          • GCC 4.3.0: 20080306

          • GCC 4.3.1: 20080606

          • GCC 4.3.2: 20080827

          • GCC 4.3.3: 20090124

          • GCC 4.3.4: 20090804

          • GCC 4.3.5: 20100522

          • GCC 4.3.6: 20110627

          • GCC 4.4.0: 20090421

          • GCC 4.4.1: 20090722

          • GCC 4.4.2: 20091015

          • GCC 4.4.3: 20100121

          • GCC 4.4.4: 20100429

          • GCC 4.4.5: 20101001

          • GCC 4.4.6: 20110416

          • GCC 4.5.0: 20100414

          • GCC 4.5.1: 20100731

          • GCC 4.5.2: 20101216

          • GCC 4.5.3: 20110428

          • GCC 4.6.0: 20110325

          • GCC 4.6.1: 20110627

          • GCC 4.6.2: 20111026

        • +

          • GCC 3.0.0: 20010615

          • GCC 3.0.1: 20010819

          • GCC 3.0.2: 20011023

          • GCC 3.0.3: 20011220

          • GCC 3.0.4: 20020220

          • GCC 3.1.0: 20020514

          • GCC 3.1.1: 20020725

          • GCC 3.2.0: 20020814

          • GCC 3.2.1: 20021119

          • GCC 3.2.2: 20030205

          • GCC 3.2.3: 20030422

          • GCC 3.3.0: 20030513

          • GCC 3.3.1: 20030804

          • GCC 3.3.2: 20031016

          • GCC 3.3.3: 20040214

          • GCC 3.4.0: 20040419

          • GCC 3.4.1: 20040701

          • GCC 3.4.2: 20040906

          • GCC 3.4.3: 20041105

          • GCC 3.4.4: 20050519

          • GCC 3.4.5: 20051201

          • GCC 3.4.6: 20060306

          • GCC 4.0.0: 20050421

          • GCC 4.0.1: 20050707

          • GCC 4.0.2: 20050921

          • GCC 4.0.3: 20060309

          • GCC 4.1.0: 20060228

          • GCC 4.1.1: 20060524

          • GCC 4.1.2: 20070214

          • GCC 4.2.0: 20070514

          • GCC 4.2.1: 20070719

          • GCC 4.2.2: 20071007

          • GCC 4.2.3: 20080201

          • GCC 4.2.4: 20080519

          • GCC 4.3.0: 20080306

          • GCC 4.3.1: 20080606

          • GCC 4.3.2: 20080827

          • GCC 4.3.3: 20090124

          • GCC 4.3.4: 20090804

          • GCC 4.3.5: 20100522

          • GCC 4.3.6: 20110627

          • GCC 4.4.0: 20090421

          • GCC 4.4.1: 20090722

          • GCC 4.4.2: 20091015

          • GCC 4.4.3: 20100121

          • GCC 4.4.4: 20100429

          • GCC 4.4.5: 20101001

          • GCC 4.4.6: 20110416

          • GCC 4.5.0: 20100414

          • GCC 4.5.1: 20100731

          • GCC 4.5.2: 20101216

          • GCC 4.5.3: 20110428

          • GCC 4.6.0: 20110325

          • GCC 4.6.1: 20110627

          • GCC 4.6.2: 20111026

        • Incremental bumping of a library pre-defined macro, _GLIBCPP_VERSION. This macro is defined as the released version of the library, as a string literal. This is only implemented in @@ -172,7 +192,7 @@ compatible. of config.h.

          It is versioned as follows: -

          • GCC 3.0.0: "3.0.0"

          • GCC 3.0.1: "3.0.0" (Error, should be "3.0.1")

          • GCC 3.0.2: "3.0.0" (Error, should be "3.0.2")

          • GCC 3.0.3: "3.0.0" (Error, should be "3.0.3")

          • GCC 3.0.4: "3.0.0" (Error, should be "3.0.4")

          • GCC 3.1.0: "3.1.0"

          • GCC 3.1.1: "3.1.1"

          • GCC 3.2.0: "3.2"

          • GCC 3.2.1: "3.2.1"

          • GCC 3.2.2: "3.2.2"

          • GCC 3.2.3: "3.2.3"

          • GCC 3.3.0: "3.3"

          • GCC 3.3.1: "3.3.1"

          • GCC 3.3.2: "3.3.2"

          • GCC 3.3.3: "3.3.3"

          • GCC 3.4: "version-unused"

          • GCC 4.x: "version-unused"

        • +

          • GCC 3.0.0: "3.0.0"

          • GCC 3.0.1: "3.0.0" (Error, should be "3.0.1")

          • GCC 3.0.2: "3.0.0" (Error, should be "3.0.2")

          • GCC 3.0.3: "3.0.0" (Error, should be "3.0.3")

          • GCC 3.0.4: "3.0.0" (Error, should be "3.0.4")

          • GCC 3.1.0: "3.1.0"

          • GCC 3.1.1: "3.1.1"

          • GCC 3.2.0: "3.2"

          • GCC 3.2.1: "3.2.1"

          • GCC 3.2.2: "3.2.2"

          • GCC 3.2.3: "3.2.3"

          • GCC 3.3.0: "3.3"

          • GCC 3.3.1: "3.3.1"

          • GCC 3.3.2: "3.3.2"

          • GCC 3.3.3: "3.3.3"

          • GCC 3.4: "version-unused"

          • GCC 4.x: "version-unused"

        • Matching each specific C++ compiler release to a specific set of C++ include files. This is only implemented in GCC 3.1.1 releases and higher. @@ -185,13 +205,13 @@ compatible. file's macro GLIBCXX_CONFIGURE (GLIBCPP_CONFIGURE before GCC 3.4.0).

          C++ includes are versioned as follows: -

          • GCC 3.0.0: include/g++-v3

          • GCC 3.0.1: include/g++-v3

          • GCC 3.0.2: include/g++-v3

          • GCC 3.0.3: include/g++-v3

          • GCC 3.0.4: include/g++-v3

          • GCC 3.1.0: include/g++-v3

          • GCC 3.1.1: include/c++/3.1.1

          • GCC 3.2.0: include/c++/3.2

          • GCC 3.2.1: include/c++/3.2.1

          • GCC 3.2.2: include/c++/3.2.2

          • GCC 3.2.3: include/c++/3.2.3

          • GCC 3.3.0: include/c++/3.3

          • GCC 3.3.1: include/c++/3.3.1

          • GCC 3.3.2: include/c++/3.3.2

          • GCC 3.3.3: include/c++/3.3.3

          • GCC 3.4.x: include/c++/3.4.x

          • GCC 4.x.y: include/c++/4.x.y

    +

    • GCC 3.0.0: include/g++-v3

    • GCC 3.0.1: include/g++-v3

    • GCC 3.0.2: include/g++-v3

    • GCC 3.0.3: include/g++-v3

    • GCC 3.0.4: include/g++-v3

    • GCC 3.1.0: include/g++-v3

    • GCC 3.1.1: include/c++/3.1.1

    • GCC 3.2.0: include/c++/3.2

    • GCC 3.2.1: include/c++/3.2.1

    • GCC 3.2.2: include/c++/3.2.2

    • GCC 3.2.3: include/c++/3.2.3

    • GCC 3.3.0: include/c++/3.3

    • GCC 3.3.1: include/c++/3.3.1

    • GCC 3.3.2: include/c++/3.3.2

    • GCC 3.3.3: include/c++/3.3.3

    • GCC 3.4.x: include/c++/3.4.x

    • GCC 4.x.y: include/c++/4.x.y

Taken together, these techniques can accurately specify interface and implementation changes in the GNU C++ tools themselves. Used properly, they allow both the GNU C++ tools implementation, and programs using them, an evolving yet controlled development that maintains backward compatibility. -

+

Prerequisites

Minimum environment that supports a versioned ABI: A supported dynamic linker, a GNU linker of sufficient vintage to understand demangled C++ name globbing (ld) or the Sun linker, a shared @@ -206,7 +226,7 @@ compatible. Most modern GNU/Linux and BSD versions, particularly ones using GCC 3.1 and later, will meet the requirements above, as does Solaris 2.5 and up. -

+

Configuring

It turns out that most of the configure options that change default behavior will impact the mangled names of exported symbols, and thus impact versioning and compatibility. @@ -224,7 +244,7 @@ compatible. attempts to make sure that all the requirement for symbol versioning are in place. For more information, please consult acinclude.m4. -

+

Checking Active

When the GNU C++ library is being built with symbol versioning on, you should see the following at configure time for libstdc++: @@ -272,16 +292,16 @@ On Solaris 2, you can use pvs -r instead: libc.so.1 (SUNWprivate_1.1, SYSVABI_1.3);

ldd -v works too, but is very verbose. -

+

Allowed Changes

The following will cause the library minor version number to increase, say from "libstdc++.so.3.0.4" to "libstdc++.so.3.0.5". -

  1. Adding an exported global or static data member

  2. Adding an exported function, static or non-virtual member function

  3. Adding an exported symbol or symbols by additional instantiations

+

  1. Adding an exported global or static data member

  2. Adding an exported function, static or non-virtual member function

  3. Adding an exported symbol or symbols by additional instantiations

Other allowed changes are possible. -

+

Prohibited Changes

The following non-exhaustive list will cause the library major version number to increase, say from "libstdc++.so.3.0.4" to "libstdc++.so.4.0.0". -

  1. Changes in the gcc/g++ compiler ABI

  2. Changing size of an exported symbol

  3. Changing alignment of an exported symbol

  4. Changing the layout of an exported symbol

  5. Changing mangling on an exported symbol

  6. Deleting an exported symbol

  7. Changing the inheritance properties of a type by adding or removing +

    1. Changes in the gcc/g++ compiler ABI

    2. Changing size of an exported symbol

    3. Changing alignment of an exported symbol

    4. Changing the layout of an exported symbol

    5. Changing mangling on an exported symbol

    6. Deleting an exported symbol

    7. Changing the inheritance properties of a type by adding or removing base classes

    8. Changing the size, alignment, or layout of types specified in the C++ standard. These may not necessarily be @@ -293,10 +313,10 @@ class that would otherwise have implicit versions. This will change the way the compiler deals with this class in by-value return statements or parameters: instead of passing instances of this class in registers, the compiler will be forced to use memory. See the -section on Function +section on Function Calling Conventions and APIs of the C++ ABI documentation for further details. -

  1. +

Implementation

  1. Separation of interface and implementation

    This is accomplished by two techniques that separate the API from @@ -344,7 +364,7 @@ exceptional symbols are allowed to be visible.

    CXXABI, select items are allowed to be visible.

  • Freezing the API

    Disallowed changes, as above, are not made on a stable release branch. Enforcement tends to be less strict with GNU extensions that -standard includes.

    • +standard includes.

    Testing

    Single ABI Testing

    Testing for GNU C++ ABI changes is composed of two distinct areas: testing the C++ compiler (g++) for compiler changes, and testing the C++ library (libstdc++) for library changes. @@ -410,7 +430,7 @@ and other detailed data is not displayed with this flag.

    Perhaps there are other C++ ABI checkers. If so, please notify us. We'd like to know about them! -

    +

    Multiple ABI Testing

    A "C" application, dynamically linked to two shared libraries, liba, libb. The dependent library liba is a C++ shared library compiled with GCC 3.3, and uses io, exceptions, locale, etc. The dependent library @@ -473,7 +493,7 @@ gcc test.c -g -O2 -L. -lone -ltwo /usr/lib/libstdc++.so.5 /usr/lib/libstdc++.so. This resulting binary, when executed, will be able to safely use code from both liba, and the dependent libstdc++.so.6, and libb, with the dependent libstdc++.so.5. -

    +

    Outstanding Issues

    Some features in the C++ language make versioning especially difficult. In particular, compiler generated constructs such as implicit instantiations for templates, typeinfo information, and @@ -483,54 +503,54 @@ gcc test.c -g -O2 -L. -lone -ltwo /usr/lib/libstdc++.so.5 /usr/lib/libstdc++.so.

    For more background on this issue, see these bugzilla entries:

    -24660: versioning weak symbols in libstdc++ +24660: versioning weak symbols in libstdc++

    -19664: libstdc++ headers should have pop/push of the visibility around the declarations -

    [biblio.abicheck] - +19664: libstdc++ headers should have pop/push of the visibility around the declarations +

    Bibliography

    [biblio.abicheck] + ABIcheck - .

    [biblio.cxxabi] - + .

    [biblio.cxxabi] + C++ ABI Summary - .

    - + .

    + Intel Compilers for Linux Compatibility with the GNU Compilers - .

    - + .

    + Linker and Libraries Guide (document 819-0690) - .

    - + .

    + Sun Studio 11: C++ Migration Guide (document 819-3689) - .

    - + .

    + How to Write Shared Libraries - . Ulrich Drepper.

    - + . Ulrich Drepper.

    + C++ ABI for the ARM Architecture - .

    - + .

    + Dynamic Shared Objects: Survey and Issues - . + . ISO C++ J16/06-0046 - . Benjamin Kosnik.

    - + . Benjamin Kosnik.

    + Versioning With Namespaces - . + . ISO C++ J16/06-0083 - . Benjamin Kosnik.

    - + . Benjamin Kosnik.

    + Binary Compatibility of Shared Libraries Implemented in C++ on GNU/Linux Systems - . + . SYRCoSE 2009 - . Pavel Shved. Denis Silakov.

    Prev Up Next
    Test Home API Evolution and Deprecation History
    + . Pavel Shved. Denis Silakov.

    Prev Up Next
    Test Home API Evolution and Deprecation History
    diff --git a/libstdc++-v3/doc/html/manual/algorithms.html b/libstdc++-v3/doc/html/manual/algorithms.html index a0d28887854..bf3cee1d07f 100644 --- a/libstdc++-v3/doc/html/manual/algorithms.html +++ b/libstdc++-v3/doc/html/manual/algorithms.html @@ -1,18 +1,28 @@ - - -Chapter 11.  Algorithms
    Chapter 11.  +Chapter 11.  Algorithms
    Chapter 11.  Algorithms -
    Prev Part II.  +
    Prev Part II.  Standard Contents -  Next
    		 Next

    Chapter 11.  Algorithms - -

    Table of Contents

    Mutating
    swap
    Specializations

    + +

    Table of Contents

    Mutating
    swap
    Specializations

    The neatest accomplishment of the algorithms section is that all the work is done via iterators, not containers directly. This means two important things: -

    1. +

      1. Anything that behaves like an iterator can be used in one of these algorithms. Raw pointers make great candidates, thus built-in arrays are fine containers, as well as your own @@ -42,7 +52,7 @@ to cause so much confusion. Once you get range into your head (it's not that hard, honest!), then the algorithms are a cakewalk. -

        If you call std::swap(x,y); where x and y are standard +

        Mutating

        swap

        Specializations

        If you call std::swap(x,y); where x and y are standard containers, then the call will automatically be replaced by a call to x.swap(y); instead.

        This allows member functions of each container class to take over, and @@ -52,10 +62,10 @@ fact use constant-time swaps.) This should not be surprising, since for two containers of the same type to swap contents, only some internal pointers to storage need to be exchanged. -

        Prev Up Next
        Chapter 10.  +

        Prev Up Next
        Chapter 10.  Iterators - Home Chapter 12.  + Home Chapter 12.  Numerics
        diff --git a/libstdc++-v3/doc/html/manual/api.html b/libstdc++-v3/doc/html/manual/api.html index a6b83886ac9..0e791310ed3 100644 --- a/libstdc++-v3/doc/html/manual/api.html +++ b/libstdc++-v3/doc/html/manual/api.html @@ -1,11 +1,19 @@ - - -API Evolution and Deprecation History
        API Evolution and Deprecation History
        Prev Appendix B.  +API Evolution and Deprecation History
        API Evolution and Deprecation History
        Prev Appendix B.  Porting and Maintenance - Next

        +

        		 Next

        API Evolution and Deprecation History

        A list of user-visible changes, in chronological order -

        +

        3.0

        Extensions moved to include/ext.

        Include files from the SGI/HP sources that pre-date the ISO standard @@ -14,7 +22,7 @@ the include/backward directory and a deprecated wa is added that notifies on inclusion (-Wno-deprecated deactivates the warning.)

        Deprecated include backward/strstream added.

        Removal of include builtinbuf.h, indstream.h, parsestream.h, PlotFile.h, SFile.h, stdiostream.h, and stream.h. -

        +

        3.1

        Extensions from SGI/HP moved from namespace std to namespace __gnu_cxx. As part of this, the following @@ -26,7 +34,7 @@ Extensions to basic_filebuf introduced: ext/rb_tree.

        Removal of ext/tree, moved to backward/tree.h. -

        +

        3.2

        Symbol versioning introduced for shared library.

        Removal of include backward/strstream.h.

        Allocator changes. Change __malloc_alloc to malloc_allocator and __new_alloc to new_allocator.

        For GCC releases from 2.95 through the 3.1 series, defining __USE_MALLOC on the gcc command line would change the default allocation strategy to instead use malloc and @@ -36,8 +44,8 @@ Removal of ext/tree, moved to GLIBCXX_FORCE_NEW in the environment, see the mt allocator chapter for details. -

        Error handling in iostreams cleaned up, made consistent.

        -

        +

        Error handling in iostreams cleaned up, made consistent.

        3.3

        +

        3.4

        Large file support.

        Extensions for generic characters and char_traits added in ext/pod_char_traits.h. @@ -78,11 +86,11 @@ _Alloc_traits have been removed. __alloc to select an underlying allocator that satisfied memory allocation requests. The selection of this underlying allocator was not user-configurable. -

        Table B.6. Extension Allocators

        Allocator (3.4)Header (3.4)Allocator (3.[0-3])Header (3.[0-3])
        __gnu_cxx::new_allocator<T>ext/new_allocator.hstd::__new_allocmemory
        __gnu_cxx::malloc_allocator<T>ext/malloc_allocator.hstd::__malloc_alloc_template<int>memory
        __gnu_cxx::debug_allocator<T>ext/debug_allocator.hstd::debug_alloc<T>memory
        __gnu_cxx::__pool_alloc<T>ext/pool_allocator.hstd::__default_alloc_template<bool,int>memory
        __gnu_cxx::__mt_alloc<T>ext/mt_allocator.h
        __gnu_cxx::bitmap_allocator<T>ext/bitmap_allocator.h

        Releases after gcc-3.4 have continued to add to the collection +

        Table B.6. Extension Allocators

        Allocator (3.4)Header (3.4)Allocator (3.[0-3])Header (3.[0-3])
        __gnu_cxx::new_allocator<T>ext/new_allocator.hstd::__new_allocmemory
        __gnu_cxx::malloc_allocator<T>ext/malloc_allocator.hstd::__malloc_alloc_template<int>memory
        __gnu_cxx::debug_allocator<T>ext/debug_allocator.hstd::debug_alloc<T>memory
        __gnu_cxx::__pool_alloc<T>ext/pool_allocator.hstd::__default_alloc_template<bool,int>memory
        __gnu_cxx::__mt_alloc<T>ext/mt_allocator.h
        __gnu_cxx::bitmap_allocator<T>ext/bitmap_allocator.h

        Releases after gcc-3.4 have continued to add to the collection of available allocators. All of these new allocators are standard-style. The following table includes details, along with the first released version of GCC that included the extension allocator. -

        Table B.7. Extension Allocators Continued

        AllocatorIncludeVersion
        __gnu_cxx::array_allocator<T>ext/array_allocator.h4.0.0
        __gnu_cxx::throw_allocator<T>ext/throw_allocator.h4.2.0

        +

        Table B.7. Extension Allocators Continued

        AllocatorIncludeVersion
        __gnu_cxx::array_allocator<T>ext/array_allocator.h4.0.0
        __gnu_cxx::throw_allocator<T>ext/throw_allocator.h4.2.0

        Debug mode first appears.

        Precompiled header support PCH support. @@ -92,7 +100,7 @@ Macro guard for changed, from _GLIBCPP_ to ext/stdio_sync_filebuf.h added.

        Extension ext/demangle.h added. -

        +

        4.0

        TR1 features first appear.

        @@ -101,14 +109,14 @@ Extension allocator ext/array_allocator.h added. Extension codecvt specializations moved to ext/codecvt_specializations.h.

        Removal of ext/demangle.h. -

        +

        4.1

        Removal of cassert from all standard headers: now has to be explicitly included for std::assert calls.

        Extensions for policy-based data structures first added. New includes, types, namespace pb_assoc.

        Extensions for typelists added in ext/typelist.h.

        Extension for policy-based basic_string first added: __gnu_cxx::__versa_string in ext/vstring.h. -

        +

        4.2

        Default visibility attributes applied to namespace std. Support for -fvisibility.

        TR1 random, complex, and C compatibility headers added.

        Extensions for concurrent programming consolidated into ext/concurrence.h and ext/atomicity.h, @@ -123,13 +131,13 @@ types, namespace moved to __pb_ds. std::__debug and extensions in namespace __gnu_cxx::__debug.

        Extensions added: ext/typelist.h and ext/throw_allocator.h. -

        +

        4.3

        C++0X features first appear.

        TR1 regex and cmath's mathematical special function added.

        Backward include edit. -

        • Removed

          +

          • Removed

            algobase.h algo.h alloc.h bvector.h complex.h defalloc.h deque.h fstream.h function.h hash_map.h hash_set.h hashtable.h heap.h iomanip.h iostream.h istream.h iterator.h @@ -141,7 +149,7 @@ Backward include edit. auto_ptr.h and binders.h

          Header dependency streamlining. -

          • algorithm no longer includes climits, cstring, or iosfwd

          • bitset no longer includes istream or ostream, adds iosfwd

          • functional no longer includes cstddef

          • iomanip no longer includes istream, istream, or functional, adds ioswd

          • numeric no longer includes iterator

          • string no longer includes algorithm or memory

          • valarray no longer includes numeric or cstdlib

          • tr1/hashtable no longer includes memory or functional

          • tr1/memory no longer includes algorithm

          • tr1/random no longer includes algorithm or fstream

          +

          • algorithm no longer includes climits, cstring, or iosfwd

          • bitset no longer includes istream or ostream, adds iosfwd

          • functional no longer includes cstddef

          • iomanip no longer includes istream, istream, or functional, adds ioswd

          • numeric no longer includes iterator

          • string no longer includes algorithm or memory

          • valarray no longer includes numeric or cstdlib

          • tr1/hashtable no longer includes memory or functional

          • tr1/memory no longer includes algorithm

          • tr1/random no longer includes algorithm or fstream

          Debug mode for unordered_map and unordered_set.

          Parallel mode first appears. @@ -155,10 +163,10 @@ Parallel mode first appears. PCH binary files no longer installed. Instead, the source files are installed.

          Namespace pb_ds moved to __gnu_pb_ds. -

        +

        4.4

        C++0X features. -

        • +

          • Added.

            atomic, @@ -210,10 +218,10 @@ and ext/extptr_allocator.h. Support for non-standard pointer types has been added to vector and forward_list. -

          +

          4.5

          C++0X features. -

          • +

            • Added.

              functional, @@ -240,4 +248,4 @@ The default behavior for comparing typeinfo names changed, so in typeinfo, __GXX_MERGED_TYPEINFO_NAMES now defaults to zero.

              Extensions modified: ext/throw_allocator.h. -

          Prev Up Next
          ABI Policy and Guidelines Home Backwards Compatibility
          +

        Prev Up Next
        ABI Policy and Guidelines Home Backwards Compatibility
        diff --git a/libstdc++-v3/doc/html/manual/appendix_contributing.html b/libstdc++-v3/doc/html/manual/appendix_contributing.html index 35842874316..7175f75865f 100644 --- a/libstdc++-v3/doc/html/manual/appendix_contributing.html +++ b/libstdc++-v3/doc/html/manual/appendix_contributing.html @@ -1,19 +1,27 @@ - - -Appendix A.  Contributing
        Appendix A.  +Appendix A.  Contributing
        Appendix A.  Contributing -
        Prev Part IV.  +
        Prev Part IV.  Appendices - Next
        		 Next

        Contributing - -

        Table of Contents

        Contributor Checklist
        Reading
        Assignment
        Getting Sources
        Submitting Patches
        Directory Layout and Source Conventions
        Coding Style
        Bad Identifiers
        By Example
        Design Notes

        + +

        Table of Contents

        Contributor Checklist
        Reading
        Assignment
        Getting Sources
        Submitting Patches
        Directory Layout and Source Conventions
        Coding Style
        Bad Identifiers
        By Example
        Design Notes

        The GNU C++ Library follows an open development model. Active contributors are assigned maintainer-ship responsibility, and given write access to the source repository. First time contributors should follow this procedure: -

        Assignment

        Small changes can be accepted without a copyright assignment form on file. New code and additions to the library need completed copyright assignment form on file at the FSF. Note: your employer may be required @@ -66,7 +74,7 @@ this question would be appreciated.

        For more information about getting a copyright assignment, please see - Legal + Legal Matters.

        Please contact Benjamin Kosnik at @@ -75,14 +83,14 @@ requesting an assignment form from , please cc the libstdc++ maintainer above so that progress can be monitored. -

        - Getting write access +

        Getting Sources

        + Getting write access (look for "Write after approval") -

        +

        Submitting Patches

        Every patch must have several pieces of information before it can be properly evaluated. Ideally (and to ensure the fastest possible response from the maintainers) it would have all of these pieces: -

        • +

          • A description of the bug and how your patch fixes this bug. For new features a description of the feature and your implementation. @@ -103,7 +111,7 @@ else, use diff -cp OLD NEW ... If your version of diff does not support these options, then get the latest version of GNU - diff. The SVN + diff. The SVN Tricks wiki page has information on customising the output of svn diff.

          • @@ -111,6 +119,6 @@ mail message and send it to libstdc++@gcc.gnu.org. All patches and related discussion should be sent to the libstdc++ mailing list. -

        Prev Up Next
        Part IV.  +

        Prev Up Next
        Part IV.  Appendices - Home Directory Layout and Source Conventions
        +         		Home Directory Layout and Source Conventions
        diff --git a/libstdc++-v3/doc/html/manual/appendix_free.html b/libstdc++-v3/doc/html/manual/appendix_free.html index dc4eddf9b46..48ec0932562 100644 --- a/libstdc++-v3/doc/html/manual/appendix_free.html +++ b/libstdc++-v3/doc/html/manual/appendix_free.html @@ -1,13 +1,21 @@ - - -Appendix C.  Free Software Needs Free Documentation
        Appendix C.  +Appendix C.  Free Software Needs Free Documentation
        Appendix C.  Free Software Needs Free Documentation -
        Prev Part IV.  +
        Prev Part IV.  Appendices - Next
        		 Next

        Free Software Needs Free Documentation - +

        The biggest deficiency in free operating systems is not in the software--it is the lack of good free manuals that we can include in @@ -41,7 +49,7 @@ can ill afford to lose manuals this way. Free documentation, like free software, is a matter of freedom, not price. The problem with these manuals was not that O'Reilly Associates charged a price for printed copies--that in itself is fine. -(The Free Software Foundation sells printed copies of +(The Free Software Foundation sells printed copies of free GNU manuals, too.) But GNU manuals are available in source code form, while these manuals are available only on paper. GNU manuals come with permission to copy and modify; the Perl manuals do not. @@ -117,10 +125,10 @@ manuals instead of proprietary ones. One way you can help this is to check the distribution terms of a manual before you buy it, and prefer copylefted manuals to non-copylefted ones.

        -[Note: We now maintain a web page +[Note: We now maintain a web page that lists free books available from other publishers].

        Copyright © 2004, 2005, 2006, 2007 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA

        Verbatim copying and distribution of this entire article are permitted worldwide, without royalty, in any medium, provided this -notice is preserved.

        Report any problems or suggestions to .

        Prev Up Next
        Backwards Compatibility Home Appendix D.  +notice is preserved.

        Report any problems or suggestions to .

        Prev Up Next
        Backwards Compatibility Home Appendix D.  GNU General Public License version 3
        diff --git a/libstdc++-v3/doc/html/manual/appendix_gfdl.html b/libstdc++-v3/doc/html/manual/appendix_gfdl.html index dc1088a241f..d0c92d09f35 100644 --- a/libstdc++-v3/doc/html/manual/appendix_gfdl.html +++ b/libstdc++-v3/doc/html/manual/appendix_gfdl.html @@ -1,14 +1,18 @@ - - -Appendix E. GNU Free Documentation License
        Appendix E. GNU Free Documentation License
        Prev Part IV.  +Appendix E. GNU Free Documentation License
        Appendix E. GNU Free Documentation License
        Prev Part IV.  Appendices - Next

        Version 1.3, 3 November 2008

        +

        		 Next

        GNU Free Documentation License

        Version 1.3, 3 November 2008

        Copyright © 2000, 2001, 2002, 2007, 2008 - Free Software Foundation, Inc. + Free Software Foundation, Inc.

        Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. -

        +

        0. PREAMBLE

        The purpose of this License is to make a manual, textbook, or other @@ -31,7 +35,7 @@ for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. -

        +

        1. APPLICABILITY AND DEFINITIONS

        This License applies to any manual or other work, in any medium, that @@ -120,7 +124,7 @@ but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. -

        +

        2. VERBATIM COPYING

        You may copy and distribute the Document in any medium, either @@ -135,7 +139,7 @@

        You may also lend copies, under the same conditions stated above, and you may publicly display copies. -

        +

        3. COPYING IN QUANTITY

        If you publish printed copies (or copies in media that commonly have @@ -169,7 +173,7 @@ It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. -

        +

        4. MODIFICATIONS

        You may copy and distribute a Modified Version of the Document under the @@ -178,7 +182,7 @@ filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: -

        1. +

          1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the @@ -269,7 +273,7 @@ The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. -

            +

            5. COMBINING DOCUMENTS

            You may combine the Document with other documents released under this @@ -294,7 +298,7 @@ Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements”. -

            +

            6. COLLECTIONS OF DOCUMENTS

            You may make a collection consisting of the Document and other documents @@ -307,7 +311,7 @@ it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. -

            +

            7. AGGREGATION WITH INDEPENDENT WORKS

            A compilation of the Document or its derivatives with other separate and @@ -325,7 +329,7 @@ bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. -

            +

            8. TRANSLATION

            Translation is considered a kind of modification, so you may distribute @@ -344,7 +348,7 @@ “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. -

            +

            9. TERMINATION

            You may not copy, modify, sublicense, or distribute the Document except as @@ -370,14 +374,14 @@ License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it. -

            +

            10. FUTURE REVISIONS OF THIS LICENSE

            The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See - Copyleft. + Copyleft.

            Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License @@ -390,7 +394,7 @@ can decide which future versions of this License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Document. -

            +

            11. RELICENSING

            “Massive Multiauthor Collaboration Site” (or “MMC @@ -419,7 +423,7 @@ The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. -

            +

            ADDENDUM: How to use this License for your documents

            To use this License in a document you have written, include a copy of the @@ -444,6 +448,6 @@ being LIST, and with the Back-Cover Texts being LIST.

            recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. -

          Prev Up Next
          Appendix D.  +

          Prev Up Next
          Appendix D.  GNU General Public License version 3 -  Home 
          +            		Home 
          diff --git a/libstdc++-v3/doc/html/manual/appendix_gpl.html b/libstdc++-v3/doc/html/manual/appendix_gpl.html index 6349cd40650..136d59cfd1c 100644 --- a/libstdc++-v3/doc/html/manual/appendix_gpl.html +++ b/libstdc++-v3/doc/html/manual/appendix_gpl.html @@ -1,20 +1,24 @@ - - -Appendix D.  GNU General Public License version 3
          Appendix D.  +Appendix D.  GNU General Public License version 3
          Appendix D.  GNU General Public License version 3 -
          Prev Part IV.  +
          Prev Part IV.  Appendices - Next
          		 Next

          GNU General Public License version 3

          Version 3, 29 June 2007

          Copyright © 2007 Free Software Foundation, Inc. - http://www.fsf.org/ + http://www.fsf.org/

          Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. -

          +

          Preamble

          The GNU General Public License is a free, copyleft @@ -78,9 +82,9 @@

          The precise terms and conditions for copying, distribution and modification follow. -

          +

          TERMS AND CONDITIONS -

          +

          0. Definitions.

          “This License” refers to version 3 of the GNU @@ -122,7 +126,7 @@ License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. -

          +

          1. Source Code.

          The “source code” for a work means the preferred form of the @@ -162,7 +166,7 @@ automatically from other parts of the Corresponding Source.

          The Corresponding Source for a work in source code form is that same work. -

          +

          2. Basic Permissions.

          All rights granted under this License are granted for the term of copyright @@ -187,7 +191,7 @@ Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. -

          +

          3. Protecting Users’ Legal Rights From Anti-Circumvention Law.

          No covered work shall be deemed part of an effective technological measure @@ -202,7 +206,7 @@ the work as a means of enforcing, against the work’s users, your or third parties’ legal rights to forbid circumvention of technological measures. -

          +

          4. Conveying Verbatim Copies.

          You may convey verbatim copies of the Program’s source code as you @@ -215,13 +219,13 @@

          You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. -

          +

          5. Conveying Modified Source Versions.

          You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: -

          1. +

            1. The work must carry prominent notices stating that you modified it, and giving a relevant date.

            2. @@ -251,13 +255,13 @@ or legal rights of the compilation’s users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. -

              +

              6. Conveying Non-Source Forms.

              You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: -

              1. +

                1. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software @@ -346,7 +350,7 @@ (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. -

                  +

                  7. Additional Terms.

                  “Additional permissions” are terms that supplement the terms of @@ -368,7 +372,7 @@ Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: -

                  1. +

                    1. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or

                    2. @@ -410,7 +414,7 @@ Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. -

                      +

                      8. Termination.

                      You may not propagate or modify a covered work except as expressly provided @@ -436,7 +440,7 @@ License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. -

                      +

                      9. Acceptance Not Required for Having Copies.

                      You are not required to accept this License in order to receive or run a @@ -447,7 +451,7 @@ These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. -

                      +

                      10. Automatic Licensing of Downstream Recipients.

                      Each time you convey a covered work, the recipient automatically receives a @@ -472,7 +476,7 @@ or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. -

                      +

                      11. Patents.

                      A “contributor” is a copyright holder who authorizes use under @@ -539,7 +543,7 @@ Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. -

                      +

                      12. No Surrender of Others’ Freedom.

                      If conditions are imposed on you (whether by court order, agreement or @@ -551,7 +555,7 @@ to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. -

                      +

                      13. Use with the GNU Affero General Public License.

                      Notwithstanding any other provision of this License, you have permission to @@ -562,7 +566,7 @@ requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. -

                      +

                      14. Revised Versions of this License.

                      The Free Software Foundation may publish revised and/or new versions of the @@ -587,7 +591,7 @@ Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. -

                      +

                      15. Disclaimer of Warranty.

                      THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE @@ -598,7 +602,7 @@ THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. -

                      +

                      16. Limitation of Liability.

                      IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL @@ -610,7 +614,7 @@ PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. -

                      +

                      17. Interpretation of Sections 15 and 16.

                      If the disclaimer of warranty and limitation of liability provided above @@ -619,9 +623,9 @@ waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. -

                      +

                      END OF TERMS AND CONDITIONS -

                      +

                      How to Apply These Terms to Your New Programs

                      If you develop a new program, and you want it to be of the greatest possible @@ -648,7 +652,7 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License -along with this program. If not, see http://www.gnu.org/licenses/. +along with this program. If not, see http://www.gnu.org/licenses/.

                      Also add information on how to contact you by electronic and paper mail.

                      @@ -669,15 +673,15 @@ under certain conditions; type ‘show c’ for det if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see - http://www.gnu.org/licenses/. + http://www.gnu.org/licenses/.

                      The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this - License. But first, please read http://www.gnu.org/philosophy/why-not-lgpl.html. -

                    Prev Up Next
                    Appendix C.  + License. But first, please read http://www.gnu.org/philosophy/why-not-lgpl.html. +

                    Prev Up Next
                    Appendix C.  Free Software Needs Free Documentation - Home Appendix E. GNU Free Documentation License
                    +                     		Home Appendix E. GNU Free Documentation License
                    diff --git a/libstdc++-v3/doc/html/manual/appendix_porting.html b/libstdc++-v3/doc/html/manual/appendix_porting.html index f92537b2918..175d509d2f9 100644 --- a/libstdc++-v3/doc/html/manual/appendix_porting.html +++ b/libstdc++-v3/doc/html/manual/appendix_porting.html @@ -1,14 +1,22 @@ - - -Appendix B.  Porting and Maintenance
                    Appendix B.  +Appendix B.  Porting and Maintenance
                    Appendix B.  Porting and Maintenance -
                    Prev Part IV.  +
                    Prev Part IV.  Appendices - Next
                    		 Next

                    Porting and Maintenance - -

                    Table of Contents

                    Configure and Build Hacking
                    Prerequisites
                    Overview: What Comes from Where
                    Storing Information in non-AC files (like configure.host)
                    Coding and Commenting Conventions
                    The acinclude.m4 layout
                    GLIBCXX_ENABLE, the --enable maker
                    Writing and Generating Documentation
                    Introduction
                    Generating Documentation
                    Doxygen
                    Prerequisites
                    Generating the Doxygen Files
                    Markup
                    Docbook
                    Prerequisites
                    Generating the DocBook Files
                    Editing and Validation
                    File Organization and Basics
                    Markup By Example
                    Porting to New Hardware or Operating Systems
                    Operating System
                    CPU
                    Character Types
                    Thread Safety
                    Numeric Limits
                    Libtool
                    Test
                    Organization
                    Directory Layout
                    Naming Conventions
                    Running the Testsuite
                    Basic
                    Variations
                    Permutations
                    Writing a new test case
                    Test Harness and Utilities
                    Dejagnu Harness Details
                    Utilities
                    Special Topics
                    + +

            Table of Contents

            Configure and Build Hacking
            Prerequisites
            Overview: What Comes from Where
            Storing Information in non-AC files (like configure.host)
            Coding and Commenting Conventions
            The acinclude.m4 layout
            GLIBCXX_ENABLE, the --enable maker
            Writing and Generating Documentation
            Introduction
            Generating Documentation
            Doxygen
            Prerequisites
            Generating the Doxygen Files
            Markup
            Docbook
            Prerequisites
            Generating the DocBook Files
            Editing and Validation
            File Organization and Basics
            Markup By Example
            Porting to New Hardware or Operating Systems
            Operating System
            CPU
            Character Types
            Thread Safety
            Numeric Limits
            Libtool
            Test
            Organization
            Directory Layout
            Naming Conventions
            Running the Testsuite
            Basic
            Variations
            Permutations
            Writing a new test case
            Test Harness and Utilities
            Dejagnu Harness Details
            Utilities
            Special Topics
            Qualifying Exception Safety Guarantees
            Overview
            @@ -30,8 +38,8 @@ Support for C++TR1 dialect. Support for C++11 dialect.
            Container::iterator_type is not necessarily Container::value_type* -

            - As noted previously, +

            Configure and Build Hacking

            Prerequisites

            + As noted previously, certain other tools are necessary for hacking on files that control configure (configure.ac, acinclude.m4) and make @@ -41,17 +49,17 @@ Support for C++11 dialect. in GCC try to stay in sync with each other in terms of versions of the auto-tools used, so please try to play nicely with the neighbors. -

            Figure B.1. Configure and Build File Dependencies

            Dependency Graph for Configure and Build Files

            +

            Overview: What Comes from Where

            Figure B.1. Configure and Build File Dependencies

            Dependency Graph for Configure and Build Files

            Regenerate all generated files by using the command sequence "autoreconf" at the top level of the libstdc++ source directory. The following will also work, but is much more complex: "aclocal-1.11 && autoconf-2.64 && autoheader-2.64 && automake-1.11" The version numbers may be absent entirely or otherwise vary depending on - the + the current requirements and your vendor's choice of installation names. -

            +

            Storing Information in non-AC files (like configure.host)

            Until that glorious day when we can use AC_TRY_LINK with a cross-compiler, we have to hardcode the results of what the tests would have shown if they could be run. So we have an inflexible @@ -73,7 +81,7 @@ Support for C++11 dialect. for instance, but then we would need arguments to aclocal/autoconf to properly find them all when generating configure. I would discourage that. -

            +

            Coding and Commenting Conventions

            Most comments should use {octothorpes, shibboleths, hash marks, pound signs, whatever} rather than "dnl". Nearly all comments in configure.ac should. Comments inside macros written in ancilliary @@ -90,7 +98,7 @@ Support for C++11 dialect. Do not use any $target* variables, such as $target_alias. The single exception is in configure.ac, for automake+dejagnu's sake. -

            +

            The acinclude.m4 layout

            The nice thing about acinclude.m4/aclocal.m4 is that macros aren't actually performed/called/expanded/whatever here, just loaded. So we can arrange the contents however we like. As of this writing, @@ -161,11 +169,11 @@ Support for C++11 dialect.

            Things which we don't seem to use directly, but just has to be present otherwise stuff magically goes wonky. -

            +

            GLIBCXX_ENABLE, the --enable maker

            All the GLIBCXX_ENABLE_FOO macros use a common helper, GLIBCXX_ENABLE. (You don't have to use it, but it's easy.) The helper does two things for us: -

            1. +

              1. Builds the call to the AC_ARG_ENABLE macro, with --help text properly quoted and aligned. (Death to changequote!)

              2. @@ -190,7 +198,7 @@ Support for C++11 dialect. GLIBCXX_ENABLE (FEATURE, DEFAULT, HELP-ARG, HELP-STRING) GLIBCXX_ENABLE (FEATURE, DEFAULT, HELP-ARG, HELP-STRING, permit a|b|c) GLIBCXX_ENABLE (FEATURE, DEFAULT, HELP-ARG, HELP-STRING, SHELL-CODE-HANDLER) -

                • +

                  • FEATURE is the string that follows --enable. The results of the test (such as it is) will be in the variable $enable_FEATURE, where FEATURE has been squashed. Example: @@ -218,7 +226,7 @@ Support for C++11 dialect.

                    If you're wondering what that line noise in the last example was, that's how you embed autoconf special characters in output text. - They're called quadrigraphs + They're called quadrigraphs and you should use them whenever necessary.

                  • HELP-STRING is what you think it is. Do not include the "default" text like we used to do; it will be done for you by @@ -249,4 +257,4 @@ Support for C++11 dialect. argument checking at all is done in this signature. See GLIBCXX_ENABLE_CXX_FLAGS for an example of handling, and an error message. -

              Prev Up Next
              Design Notes Home Writing and Generating Documentation
              +

            Prev Up Next
            Design Notes Home Writing and Generating Documentation
            diff --git a/libstdc++-v3/doc/html/manual/associative.html b/libstdc++-v3/doc/html/manual/associative.html index 587b75643b9..26aae420a8a 100644 --- a/libstdc++-v3/doc/html/manual/associative.html +++ b/libstdc++-v3/doc/html/manual/associative.html @@ -1,9 +1,17 @@ - - -Associative
            Associative
            Prev Chapter 9.  +Associative
            Associative
            Prev Chapter 9.  Containers - Next

            +

            		 Next

            Associative

            Insertion Hints

            Section [23.1.2], Table 69, of the C++ standard lists this function for all of the associative containers (map, set, etc): 

            @@ -13,7 +21,7 @@
      item to insert.  The standard says that “t is
      inserted as close as possible to the position just prior to
      p.” (Library DR #233 addresses this topic,
-     referring to N1780.
+     referring to N1780.
      Since version 4.2 GCC implements the resolution to DR 233, so
      that insertions happen as close as possible to the hint. For
      earlier releases the hint was only used as described below.
@@ -39,7 +47,7 @@
      paragraph.  *grin*
    
            
      If the hint parameter ('p' above) is equivalent to:
-   
            • 
+   
              • 
 	  begin(), then the item being inserted should
 	  have a key less than all the other keys in the container.
 	  The item will be inserted at the beginning of the container,
@@ -84,7 +92,7 @@
      the new item would in fact belong there.  If the hint does not
      point to the correct place, then no further local searching is
      done; the search begins from scratch in logarithmic time.
-   
              
+   
              bitset
              Size Variable
              
 	No, you cannot write code of the form
       
                     #include <bitset>
@@ -102,7 +110,7 @@
      There are a couple of ways to handle this kind of thing.  Please
      consider all of them before passing judgement.  They include, in
      no chaptericular order:
-   
              • A very large N in bitset<N>.
              • A container<bool>.
              • Extremely weird solutions.
              
+   
              • A very large N in bitset<N>.
              • A container<bool>.
              • Extremely weird solutions.
              
      A very large N in
      bitset<N>.   It has been
      pointed out a few times in newsgroups that N bits only takes up
@@ -169,7 +177,7 @@
    
              
      Also note that the implementation of bitset used in libstdc++ has
      some extensions.
-   
              
+   
              Type String
              
       
              
      Bitmasks do not take char* nor const char* arguments in their
      constructors.  This is something of an accident, but you can read
@@ -186,7 +194,7 @@
      instead of
    
                     std::bitset<5> b ( “10110” );    // invalid
-    
              Prev Up Next
              Chapter 9. 
+    
              Prev Up Next
              Chapter 9. 
   Containers
   
- Home Interacting with C
              
+               		Home Interacting with C
              
diff --git a/libstdc++-v3/doc/html/manual/atomics.html b/libstdc++-v3/doc/html/manual/atomics.html
index c2a9edbbb09..eb636c5644e 100644
--- a/libstdc++-v3/doc/html/manual/atomics.html
+++ b/libstdc++-v3/doc/html/manual/atomics.html
@@ -1,16 +1,26 @@
-
-
-Chapter 14.  Atomics
              Chapter 14. 
+Chapter 14.  Atomics
              Chapter 14. 
   Atomics
   
-
              Prev Part II. 
+
              Prev Part II. 
     Standard Contents
-   Next
              		 Next
              Chapter 14. 
   Atomics
-  
-
              Table of Contents
              API Reference
              
+  
+

        Table of Contents

        API Reference

        Facilities for atomic operations. -

        +

        API Reference

        All items are declared in the standard header file atomic.

        @@ -25,7 +35,7 @@ atomic<int>.

        Full API details. -

        Prev Up Next
        Interacting with C Home Chapter 15.  +

        Prev Up Next
        Interacting with C Home Chapter 15.  Concurrency
        diff --git a/libstdc++-v3/doc/html/manual/backwards.html b/libstdc++-v3/doc/html/manual/backwards.html index d2a7d1e9359..a5984877151 100644 --- a/libstdc++-v3/doc/html/manual/backwards.html +++ b/libstdc++-v3/doc/html/manual/backwards.html @@ -1,9 +1,21 @@ - - -Backwards Compatibility
        Backwards Compatibility
        Prev Appendix B.  +Backwards Compatibility
        Backwards Compatibility
        Prev Appendix B.  Porting and Maintenance - Next

        The first generation GNU C++ library was called libg++. It was a +

        		 Next

        Backwards Compatibility

        First

        The first generation GNU C++ library was called libg++. It was a separate GNU project, although reliably paired with GCC. Rumors imply that it had a working relationship with at least two kinds of dinosaur. @@ -17,8 +29,8 @@ ISO Standard (e.g., statistical analysis). While there are a lot of really useful things that are used by a lot of people, the Standards Committee couldn't include everything, and so a lot of those “obvious” classes didn't get included. -

        Known Issues include many of the limitations of its immediate ancestor.

        Portability notes and known implementation limitations are as follows.

        At least some older implementations don't have std::ios_base, so you should use std::ios::badbit, std::ios::failbit and std::ios::eofbit and std::ios::goodbit. -

        +

        Known Issues include many of the limitations of its immediate ancestor.

        Portability notes and known implementation limitations are as follows.

        No ios_base

        At least some older implementations don't have std::ios_base, so you should use std::ios::badbit, std::ios::failbit and std::ios::eofbit and std::ios::goodbit. +

        No cout in <ostream.h>, no cin in <istream.h>

        In earlier versions of the standard, <fstream.h>, <ostream.h> @@ -29,10 +41,10 @@ Committee couldn't include everything, and so a lot of those explicitly to get the required definitions.

        Some include adjustment may be required.

        This project is no longer maintained or supported, and the sources archived. For the desperate, -the GCC extensions +the GCC extensions page describes where to find the last libg++ source. The code is considered replaced and rewritten. -

        +

        Second

        The second generation GNU C++ library was called libstdc++, or libstdc++-v2. It spans the time between libg++ and pre-ISO C++ standardization and is usually associated with the following GCC @@ -44,7 +56,7 @@ considered replaced and rewritten. archived. The code is considered replaced and rewritten.

        Portability notes and known implementation limitations are as follows. -

        +

        Namespace std:: not supported

        Some care is required to support C++ compiler and or library implementation that do not have the standard library in namespace std. @@ -108,10 +120,10 @@ AC_DEFUN([AC_CXX_NAMESPACE_STD], [ AC_DEFINE(HAVE_NAMESPACE_STD,,[Define if g++ supports namespace std. ]) fi ]) -

        +

        Illegal iterator usage

        The following illustrate implementation-allowed illegal iterator use, and then correct use. -

        • +

          • you cannot do ostream::operator<<(iterator) to print the address of the iterator => use operator<< &*iterator instead @@ -121,7 +133,7 @@ AC_DEFUN([AC_CXX_NAMESPACE_STD], [

          • if (iterator) won't work any more => use if (iterator != iterator_type()) -

        isspace from <cctype> is a macro

        Glibc 2.0.x and 2.1.x define <ctype.h> functionality as macros (isspace, isalpha etc.). @@ -155,7 +167,7 @@ std:: (__ctype_b[(int) ( ( 'X' ) )] & (unsigned short int) _ISspace ) ; (<ctype.h>) and the definitions in namespace std:: (<cctype>). -

        +

        No vector::at, deque::at, string::at

        One solution is to add an autoconf-test for this: 

         AC_MSG_CHECKING(for container::at)
@@ -181,7 +193,7 @@ AC_DEFINE(HAVE_CONTAINER_AT)],

        If you are using other (non-GNU) compilers it might be a good idea to check for string::at separately. -

        +

        No std::char_traits<char>::eof

        Use some kind of autoconf test, plus this: 

         #ifdef HAVE_CHAR_TRAITS
@@ -189,7 +201,7 @@ AC_DEFINE(HAVE_CONTAINER_AT)],
 #else
 #define CPP_EOF EOF
 #endif
-

        +

        No string::clear

        There are two functions for deleting the contents of a string: clear and erase (the latter returns the string). @@ -207,18 +219,18 @@ erase(size_type __pos = 0, size_type __n = npos) Unfortunately, clear is not implemented in this version, so you should use erase (which is probably faster than operator=(charT*)). -

        Removal of ostream::form and istream::scan extensions

        These are no longer supported. Please use stringstreams instead. -

        +

        No basic_stringbuf, basic_stringstream

        Although the ISO standard i/ostringstream-classes are provided, (<sstream>), for compatibility with older implementations the pre-ISO i/ostrstream (<strstream>) interface is also provided, with these caveats: -