diff options
Diffstat (limited to 'libstdc++-v3/docs')
| -rw-r--r-- | libstdc++-v3/docs/html/configopts.html | 16 | ||||
| -rw-r--r-- | libstdc++-v3/docs/html/debug.html | 38 | ||||
| -rw-r--r-- | libstdc++-v3/docs/html/debug_mode.html | 82 |
3 files changed, 64 insertions, 72 deletions
diff --git a/libstdc++-v3/docs/html/configopts.html b/libstdc++-v3/docs/html/configopts.html index b396a2d1822..a027c658c37 100644 --- a/libstdc++-v3/docs/html/configopts.html +++ b/libstdc++-v3/docs/html/configopts.html @@ -277,14 +277,18 @@ options</a></h1> </dd> <dt><code>--enable-symvers[=style] </code></dt> + <dd><p>In 3.1 and later, tries to turn on symbol versioning in the - shared library (if a shared library has been requested). The - only 'style' currently supported is 'gnu' which requires that - a recent version of the GNU linker be in use. With no style - given, the configure script will try to guess if the 'gnu' - style can be used, and if so, will turn it on. Hopefully - people will volunteer to do other 'style' options. + shared library (if a shared library has been + requested). Values for 'style' that are currently supported + are 'gnu', 'gnu-versioned-namespace', 'darwin', and + 'darwin-export'. Both gnu- options require that a recent + version of the GNU linker be in use. Both darwin options are + equivalent. With no style given, the configure script will try + to guess if the 'gnu' style can be used, and if so, will turn + it on. </p> + </dd> <dt><code>--enable-libstdcxx-pch </code></dt> diff --git a/libstdc++-v3/docs/html/debug.html b/libstdc++-v3/docs/html/debug.html index 0242d4363e3..6bea7f41e7a 100644 --- a/libstdc++-v3/docs/html/debug.html +++ b/libstdc++-v3/docs/html/debug.html @@ -163,91 +163,91 @@ <tr> <td>std::bitset</td> <td><bitset></td> - <td>__gnu_debug::bitset</td> + <td>debug::bitset</td> <td><debug/bitset></td> </tr> <tr> <td>std::deque</td> <td><deque></td> - <td>__gnu_debug::deque</td> + <td>debug::deque</td> <td><debug/deque></td> </tr> <tr> <td>std::list</td> <td><list></td> - <td>__gnu_debug::list</td> + <td>debug::list</td> <td><debug/list></td> </tr> <tr> <td>std::map</td> <td><map></td> - <td>__gnu_debug::map</td> + <td>debug::map</td> <td><debug/map></td> </tr> <tr> <td>std::multimap</td> <td><map></td> - <td>__gnu_debug::multimap</td> + <td>debug::multimap</td> <td><debug/map></td> </tr> <tr> <td>std::multiset</td> <td><set></td> - <td>__gnu_debug::multiset</td> + <td>debug::multiset</td> <td><debug/set></td> </tr> <tr> <td>std::set</td> <td><set></td> - <td>__gnu_debug::set</td> + <td>debug::set</td> <td><debug/set></td> </tr> <tr> <td>std::string</td> <td><string></td> - <td>__gnu_debug::string</td> + <td>debug::string</td> <td><debug/string></td> </tr> <tr> <td>std::wstring</td> <td><string></td> - <td>__gnu_debug::wstring</td> + <td>debug::wstring</td> <td><debug/string></td> </tr> <tr> <td>std::basic_string</td> <td><string></td> - <td>__gnu_debug::basic_string</td> + <td>debug::basic_string</td> <td><debug/string></td> </tr> <tr> <td>std::vector</td> <td><vector></td> - <td>__gnu_debug::vector</td> + <td>debug::vector</td> <td><debug/vector></td> </tr> <tr> <td>__gnu_cxx::hash_map</td> <td><ext/hash_map></td> - <td>__gnu_debug::hash_map</td> + <td>debug::hash_map</td> <td><debug/hash_map></td> </tr> <tr> <td>__gnu_cxx::hash_multimap</td> <td><ext/hash_map></td> - <td>__gnu_debug::hash_multimap</td> + <td>debug::hash_multimap</td> <td><debug/hash_map></td> </tr> <tr> <td>__gnu_cxx::hash_set</td> <td><ext/hash_set></td> - <td>__gnu_debug::hash_set</td> + <td>debug::hash_set</td> <td><debug/hash_set></td> </tr> <tr> <td>__gnu_cxx::hash_multiset</td> <td><ext/hash_set></td> - <td>__gnu_debug::hash_multiset</td> + <td>debug::hash_multiset</td> <td><debug/hash_set></td> </tr> </table> @@ -297,16 +297,16 @@ <li><code>std::basic_string</code> (no safe iterators)</li> <li><code>std::bitset</code></li> <li><code>std::deque</code></li> - <li><code>__gnu_cxx::hash_map</code></li> - <li><code>__gnu_cxx::hash_multimap</code></li> - <li><code>__gnu_cxx::hash_multiset</code></li> - <li><code>__gnu_cxx::hash_set</code></li> <li><code>std::list</code></li> <li><code>std::map</code></li> <li><code>std::multimap</code></li> <li><code>std::multiset</code></li> <li><code>std::set</code></li> <li><code>std::vector</code></li> + <li><code>__gnu_cxx::hash_map</code></li> + <li><code>__gnu_cxx::hash_multimap</code></li> + <li><code>__gnu_cxx::hash_multiset</code></li> + <li><code>__gnu_cxx::hash_set</code></li> </ul> diff --git a/libstdc++-v3/docs/html/debug_mode.html b/libstdc++-v3/docs/html/debug_mode.html index b62ad8f5572..e531fd3fa26 100644 --- a/libstdc++-v3/docs/html/debug_mode.html +++ b/libstdc++-v3/docs/html/debug_mode.html @@ -330,68 +330,56 @@ template<typename _Tp, typename _Allocator = allocator<_Tp> <p>In release mode, we define only the release-mode version of the component with its standard name and do not include the debugging component at all. The release mode version is defined within the - namespace <code>__gnu_norm</code>, and then associated with namespace - <code>std</code> via a "strong using" directive. Minus the - namespace associations, this method leaves the behavior of release - mode completely unchanged from its behavior prior to the - introduction of the libstdc++ debug mode. Here's an example of what - this ends up looking like, in C++.</p> + namespace <code>std</code>. Minus the namespace associations, this + method leaves the behavior of release mode completely unchanged from + its behavior prior to the introduction of the libstdc++ debug + mode. Here's an example of what this ends up looking like, in + C++.</p> <pre> -namespace __gnu_norm +namespace std { - using namespace std; - template<typename _Tp, typename _Alloc = allocator<_Tp> > class list { // ... - }; -} // namespace __gnu_norm - -namespace std -{ - using namespace __gnu_norm __attribute__ ((strong)); -} + }; +} // namespace std </pre> -<p>In debug mode we include the release-mode container and also the -debug-mode container. The release mode version is defined exactly as -before, and the debug-mode container is defined within the namespace -<code>__gnu_debug</code>, which is associated with namespace +<p>In debug mode we include the release-mode container (which is now +defined in in the namespace <code>__gnu_norm</code>) and also the +debug-mode container. The debug-mode container is defined within the +namespace <code>__gnu_debug</code>, which is associated with namespace <code>std</code> via a "strong using" directive. This method allows the debug- and release-mode versions of the same component to coexist -at compile-time without causing an unreasonable maintenance burden, -while minimizing confusion. Again, this boils down to C++ code as -follows:</p> +at compile-time and link-time without causing an unreasonable +maintenance burden, while minimizing confusion. Again, this boils down +to C++ code as follows:</p> <pre> -namespace __gnu_norm -{ - using namespace std; - - template<typename _Tp, typename _Alloc = allocator<_Tp> > - class list - { - // ... - }; -} // namespace __gnu_norm - -namespace __gnu_debug -{ - using namespace std; - - template<typename _Tp, typename _Alloc = allocator<_Tp> > - class list - : public __gnu_norm::list<_Tp, _Alloc>, - public __gnu_debug::_Safe_sequence<list<_Tp, _Alloc> > - { - // ... - }; -} // namespace __gnu_norm - namespace std { + namespace __gnu_norm + { + template<typename _Tp, typename _Alloc = allocator<_Tp> > + class list + { + // ... + }; + } // namespace __gnu_norm + + namespace __gnu_debug + { + template<typename _Tp, typename _Alloc = allocator<_Tp> > + class list + : public __gnu_norm::list<_Tp, _Alloc>, + public __gnu_debug::_Safe_sequence<list<_Tp, _Alloc> > + { + // ... + }; + } // namespace __gnu_norm + using namespace __gnu_debug __attribute__ ((strong)); } </pre> |