From: Paolo Carlini Date: Sun, 23 Mar 2008 19:19:05 +0000 (+0000) Subject: faq.xml: Fix various links. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=7d9492256aceb2fa94ec09d9a81db67b3d624472;p=gcc.git faq.xml: Fix various links. 2008-03-23 Paolo Carlini * doc/xml/faq.xml: Fix various links. * doc/xml/api.xml: Likewise. * doc/xml/manual/parallel_mode.xml: Likewise. * doc/html/faq.html: Regenerate. * doc/html/api.html: Likewise. * doc/html/manual/bk01pt12ch31s03.html: Likewise. From-SVN: r133463 --- diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index a48967dcad7..c6b52a80986 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,12 @@ +2008-03-23 Paolo Carlini + + * doc/xml/faq.xml: Fix various links. + * doc/xml/api.xml: Likewise. + * doc/xml/manual/parallel_mode.xml: Likewise. + * doc/html/faq.html: Regenerate. + * doc/html/api.html: Likewise. + * doc/html/manual/bk01pt12ch31s03.html: Likewise. + 2008-03-20 Benjamin Kosnik * testsuite/util/testsuite_abi.cc: Add support for not counting diff --git a/libstdc++-v3/doc/html/api.html b/libstdc++-v3/doc/html/api.html index f9f7e65b0f7..dd895fc5506 100644 --- a/libstdc++-v3/doc/html/api.html +++ b/libstdc++-v3/doc/html/api.html @@ -3,9 +3,9 @@ API and Source Level Documentation
API and Source Level Documentation
Prev  Next

API and Source Level Documentation

Copyright © 2008 - FSF + FSF -

diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html index 966f55a2536..b46c2b7ab5a 100644 --- a/libstdc++-v3/doc/html/faq.html +++ b/libstdc++-v3/doc/html/faq.html @@ -164,7 +164,7 @@

1.5.

How do I contribute to the effort?

- Here is a page devoted to + 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 contribute, or if you have spare time and want to @@ -320,7 +320,7 @@

If the only functions from libstdc++.a which you need are language support functions (those listed in - clause 18 of the + clause 18 of the standard, e.g., new and delete), then try linking against libsupc++.a, which is a subset of @@ -578,13 +578,13 @@ reason is that the state flags are not cleared on a successful call to open(). The standard unfortunately did not specify behavior in this case, and to everybody's great sorrow, - the proposed LWG resolution in + the proposed LWG resolution in DR #22 is to leave the flags unchanged. You must insert a call to fs.clear() between the calls to close() and open(), and then everything will work like we all expect it to work. Update: for GCC 4.0 we implemented the resolution - of DR #409 and open() now calls - clear() on success! + of DR #409 and open() + now calls clear() on success!

6.2.

-Weffc++ complains too much

@@ -647,7 +647,7 @@

More information, including how to optionally enable/disable the checks, is available - here. + here.

6.6.

Program crashes when using library code in a dynamically-loaded library @@ -672,19 +672,19 @@

A few people have reported that the standard containers appear to leak memory when tested with memory checkers such as - valgrind. + valgrind. The library's default 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 lost, memory debugging tools can report it as a leak. If you want to test the library for memory leaks please read - Tips for memory leak hunting + Tips for memory leak hunting first.

6.8.

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

See - the Containers + the Containers chapter.

6.9.

Aw, that's easy to fix! @@ -695,7 +695,7 @@ 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++ - contributors' page + contributors' page also talks about how to submit patches.

In addition to the description, the patch, and the ChangeLog @@ -868,6 +868,6 @@     

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

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

Prev Up 
 Home 
diff --git a/libstdc++-v3/doc/html/manual/bk01pt12ch31s03.html b/libstdc++-v3/doc/html/manual/bk01pt12ch31s03.html index 0bc7ae5d2ab..97fdb5ba1b5 100644 --- a/libstdc++-v3/doc/html/manual/bk01pt12ch31s03.html +++ b/libstdc++-v3/doc/html/manual/bk01pt12ch31s03.html @@ -2,7 +2,7 @@ Using
Using
Prev Chapter 31. Parallel Mode Next

Using

Using Parallel Mode

To use the libstdc++ parallel mode, compile your application with the compiler flag -D_GLIBCXX_PARALLEL -fopenmp. This - will link in libgomp, the GNU OpenMP implementation, + will link in libgomp, the GNU OpenMP implementation, whose presence is mandatory. In addition, hardware capable of atomic operations is mandatory. Actually activating these atomic operations may require explicit compiler flags on some targets diff --git a/libstdc++-v3/doc/xml/api.xml b/libstdc++-v3/doc/xml/api.xml index bd38e8392cc..506f631ba0a 100644 --- a/libstdc++-v3/doc/xml/api.xml +++ b/libstdc++-v3/doc/xml/api.xml @@ -15,7 +15,7 @@ 2008 - FSF + FSF diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml index 629d1ec12a6..a60bee3e287 100644 --- a/libstdc++-v3/doc/xml/faq.xml +++ b/libstdc++-v3/doc/xml/faq.xml @@ -130,8 +130,8 @@ - Here is a page devoted to - this topic. Subscribing to the mailing list (see above, or + 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 contribute, or if you have spare time and want to help. Contributions don't have to be in the form of source code; @@ -400,7 +400,7 @@ If the only functions from libstdc++.a which you need are language support functions (those listed in - clause 18 of the + clause 18 of the standard, e.g., new and delete), then try linking against libsupc++.a, which is a subset of @@ -785,13 +785,13 @@ reason is that the state flags are not cleared on a successful call to open(). The standard unfortunately did not specify behavior in this case, and to everybody's great sorrow, - the proposed LWG resolution in - DR #22 is to leave the flags unchanged. You must insert a call + the proposed LWG resolution in + DR #22 is to leave the flags unchanged. You must insert a call to fs.clear() between the calls to close() and open(), and then everything will work like we all expect it to work. Update: for GCC 4.0 we implemented the resolution - of DR #409 and open() now calls - clear() on success! + of DR #409 and open() + now calls clear() on success! @@ -895,7 +895,7 @@ More information, including how to optionally enable/disable the checks, is available - here. + here. @@ -940,13 +940,13 @@ A few people have reported that the standard containers appear to leak memory when tested with memory checkers such as - valgrind. + valgrind. The library's default 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 lost, memory debugging tools can report it as a leak. If you want to test the library for memory leaks please read - Tips for memory leak hunting + Tips for memory leak hunting first. @@ -961,7 +961,7 @@ See - the Containers + the Containers chapter. @@ -981,7 +981,7 @@ 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++ - contributors' page + contributors' page also talks about how to submit patches. @@ -1237,8 +1237,8 @@ The copy will take O(n) time and the swap is constant time. - See Shrink-to-fit - strings for a similar solution for strings. + See Shrink-to-fit + strings for a similar solution for strings. diff --git a/libstdc++-v3/doc/xml/manual/parallel_mode.xml b/libstdc++-v3/doc/xml/manual/parallel_mode.xml index 0bcbbcab04d..449cbda29b6 100644 --- a/libstdc++-v3/doc/xml/manual/parallel_mode.xml +++ b/libstdc++-v3/doc/xml/manual/parallel_mode.xml @@ -116,7 +116,7 @@ It might work with other compilers, though. To use the libstdc++ parallel mode, compile your application with the compiler flag -D_GLIBCXX_PARALLEL -fopenmp. This - will link in libgomp, the GNU OpenMP implementation, + will link in libgomp, the GNU OpenMP implementation, whose presence is mandatory. In addition, hardware capable of atomic operations is mandatory. Actually activating these atomic operations may require explicit compiler flags on some targets