+2008-03-23 Paolo Carlini <pcarlini@suse.de>
+
+ * 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 <bkoz@redhat.com>
* testsuite/util/testsuite_abi.cc: Add support for not counting
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>API and Source Level Documentation</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="spine.html" title="The GNU C++ Library Documentation" /><link rel="up" href="bk02.html" title="" /><link rel="prev" href="bk02.html" title="" /><link rel="next" href="bk03.html" title="" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">API and Source Level Documentation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bk02.html">Prev</a> </td><th width="60%" align="center"></th><td width="20%" align="right"> <a accesskey="n" href="bk03.html">Next</a></td></tr></table><hr /></div><div class="article" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="api"></a>API and Source Level Documentation</h2></div><div><p class="copyright">Copyright ©
2008
- <a class="ulink" href="http://fsf.org" target="_top">FSF
+ <a class="ulink" href="http://www.fsf.org/" target="_top">FSF
</a>
- </p></div><div><div class="legalnotice"><a id="id3
30876"></a><p>
+ </p></div><div><div class="legalnotice"><a id="id3
75791"></a><p>
<a class="ulink" href="17_intro/license.html" target="_top">License
</a>
</p></div></div></div><hr /></div><p>
</p></td></tr><tr class="question"><td align="left" valign="top"><a id="faq.how"></a><a id="q-how"></a><p><b>1.5.</b></p></td><td align="left" valign="top"><p>
How do I contribute to the effort?
</p></td></tr><tr class="answer"><td align="left" valign="top"><a id="a-how"></a></td><td align="left" valign="top"><p>
- Here is <a class="ulink" href="../17_intro/contribute.html" target="_top">a page devoted to
+ Here is <a class="link" href="manual/appendix_contributing.html" title="Appendix A. Contributing">a page devoted to
this topic</a>. 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
</p></td></tr><tr class="answer"><td align="left" valign="top"><a id="a-what_is_libsupcxx"></a></td><td align="left" valign="top"><p>
If the only functions from <code class="filename">libstdc++.a</code>
which you need are language support functions (those listed in
- <a class="ulink" href="../18_support/howto.html" target="_top">clause 18</a> of the
+ <a class="link" href="manual/support.html" title="Part II. Support">clause 18</a> of the
standard, e.g., <code class="function">new</code> and
<code class="function">delete</code>), then try linking against
<code class="filename">libsupc++.a</code>, which is a subset of
reason is that the state flags are <span class="emphasis"><em>not</em></span> cleared
on a successful call to open(). The standard unfortunately did
not specify behavior in this case, and to everybody's great sorrow,
- the <a class="ulink" href="../ext/howto.html#5" target="_top">proposed LWG resolution in
+ the <a class="link" href="manual/bk01pt01ch01s03.html" title="Bugs">proposed LWG resolution in
DR #22</a> is to leave the flags unchanged. You must insert a call
to <code class="function">fs.clear()</code> between the calls to close() and open(),
and then everything will work like we all expect it to work.
<span class="emphasis"><em>Update:</em></span> for GCC 4.0 we implemented the resolution
- of <a class="ulink" href="../ext/howto.html#5" target="_top">DR #409</a> and open() now calls
- <code class="function">clear()</code> on success!
+ of <a class="link" href="manual/bk01pt01ch01s03.html" title="Bugs">DR #409</a> and open()
+ now calls <code class="function">clear()</code> on success!
</p></td></tr><tr class="question"><td align="left" valign="top"><a id="faq.wefcxx_verbose"></a><a id="q-wefcxx_verbose"></a><p><b>6.2.</b></p></td><td align="left" valign="top"><p>
-Weffc++ complains too much
</p></td></tr><tr class="answer"><td align="left" valign="top"><a id="a-wefcxx_verbose"></a></td><td align="left" valign="top"><p>
</p><p>
More information, including how to optionally enable/disable the
checks, is available
- <a class="ulink" href="../19_diagnostics/howto.html#3" target="_top">here</a>.
+ <a class="link" href="manual/bk01pt03ch08.html" title="Chapter 8. Concept Checking">here</a>.
</p></td></tr><tr class="question"><td align="left" valign="top"><a id="faq.dlopen_crash"></a><a id="q-dlopen_crash"></a><p><b>6.6.</b></p></td><td align="left" valign="top"><p>
Program crashes when using library code in a
dynamically-loaded library
</p></td></tr><tr class="answer"><td align="left" valign="top"><a id="a-memory_leaks"></a></td><td align="left" valign="top"><p>
A few people have reported that the standard containers appear
to leak memory when tested with memory checkers such as
- <a class="ulink" href="http://developer.kde.org/~sewardj/" target="_top">valgrind</a>.
+ <a class="ulink" href="http://valgrind.org/" target="_top">valgrind</a>.
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
- <a class="ulink" href="../debug.html#mem" target="_top">Tips for memory leak hunting</a>
+ <a class="link" href="manual/debug.html#debug.memory" title="Memory Leak Hunting">Tips for memory leak hunting</a>
first.
</p></td></tr><tr class="question"><td align="left" valign="top"><a id="faq.list_size_on"></a><a id="q-list_size_on"></a><p><b>6.8.</b></p></td><td align="left" valign="top"><p>
list::size() is O(n)!
</p></td></tr><tr class="answer"><td align="left" valign="top"><a id="a-list_size_on"></a></td><td align="left" valign="top"><p>
See
- the <a class="ulink" href="../23_containers/howto.html#6" target="_top">Containers</a>
+ the <a class="link" href="manual/containers.html" title="Part VII. Containers">Containers</a>
chapter.
</p></td></tr><tr class="question"><td align="left" valign="top"><a id="faq.easy_to_fix"></a><a id="q-easy_to_fix"></a><p><b>6.9.</b></p></td><td align="left" valign="top"><p>
Aw, that's easy to fix!
patches</a> 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++
- <a class="ulink" href="../17_intro/contribute.html" target="_top">contributors' page</a>
+ <a class="link" href="manual/appendix_contributing.html" title="Appendix A. Contributing">contributors' page</a>
also talks about how to submit patches.
</p><p>
In addition to the description, the patch, and the ChangeLog
</p></div><p>
The copy will take O(n) time and the swap is constant time.
</p><p>
- See <a class="ulink" href="../21_strings/howto.html#6" target="_top">Shrink-to-fit
+ See <a class="link" href="manual/bk01pt05ch13s05.html" title="Shrink to Fit">Shrink-to-fit
strings</a> for a similar solution for strings.
</p></td></tr></tbody></table></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bk03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="bk03.html">Up</a></td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"><a accesskey="h" href="spine.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Using</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><meta name="keywords" content=" C++ , library , parallel " /><meta name="keywords" content=" ISO C++ , library " /><link rel="start" href="../spine.html" title="The GNU C++ Library Documentation" /><link rel="up" href="parallel_mode.html" title="Chapter 31. Parallel Mode" /><link rel="prev" href="bk01pt12ch31s02.html" title="Semantics" /><link rel="next" href="bk01pt12ch31s04.html" title="Design" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Using</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bk01pt12ch31s02.html">Prev</a> </td><th width="60%" align="center">Chapter 31. Parallel Mode</th><td width="20%" align="right"> <a accesskey="n" href="bk01pt12ch31s04.html">Next</a></td></tr></table><hr /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="manual.ext.parallel_mode.using"></a>Using</h2></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="parallel_mode.using.parallel_mode"></a>Using Parallel Mode</h3></div></div></div><p>To use the libstdc++ parallel mode, compile your application with
the compiler flag <code class="code">-D_GLIBCXX_PARALLEL -fopenmp</code>. This
- will link in <code class="code">libgomp</code>, the GNU OpenMP <a class="ulink" href="http://gcc.gnu.org/onlinedocs/libgomp" target="_top">implementation</a>,
+ will link in <code class="code">libgomp</code>, the GNU OpenMP <a class="ulink" href="http://gcc.gnu.org/onlinedocs/libgomp/" target="_top">implementation</a>,
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
2008
</year>
<holder>
- <ulink url="http://fsf.org">FSF
+ <ulink url="http://www.fsf.org/">FSF
</ulink>
</holder>
</copyright>
</question>
<answer id="a-how">
<para>
- Here is <ulink url="../17_intro/contribute.html">a page devoted to
- this topic</ulink>. Subscribing to the mailing list (see above, or
+ Here is <link linkend="appendix.contrib">a page devoted to
+ this topic</link>. 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;
<para>
If the only functions from <filename>libstdc++.a</filename>
which you need are language support functions (those listed in
- <ulink url="../18_support/howto.html">clause 18</ulink> of the
+ <link linkend="manual.support">clause 18</link> of the
standard, e.g., <function>new</function> and
<function>delete</function>), then try linking against
<filename>libsupc++.a</filename>, which is a subset of
reason is that the state flags are <emphasis>not</emphasis> cleared
on a successful call to open(). The standard unfortunately did
not specify behavior in this case, and to everybody's great sorrow,
- the <ulink url="../ext/howto.html#5">proposed LWG resolution in
- DR #22</ulink> is to leave the flags unchanged. You must insert a call
+ the <link linkend="manual.intro.status.bugs">proposed LWG resolution in
+ DR #22</link> is to leave the flags unchanged. You must insert a call
to <function>fs.clear()</function> between the calls to close() and open(),
and then everything will work like we all expect it to work.
<emphasis>Update:</emphasis> for GCC 4.0 we implemented the resolution
- of <ulink url="../ext/howto.html#5">DR #409</ulink> and open() now calls
- <function>clear()</function> on success!
+ of <link linkend="manual.intro.status.bugs">DR #409</link> and open()
+ now calls <function>clear()</function> on success!
</para>
</answer>
</qandaentry>
<para>
More information, including how to optionally enable/disable the
checks, is available
- <ulink url="../19_diagnostics/howto.html#3">here</ulink>.
+ <link linkend="manual.diagnostics.concept_checking">here</link>.
</para>
</answer>
</qandaentry>
<para>
A few people have reported that the standard containers appear
to leak memory when tested with memory checkers such as
- <ulink url="http://developer.kde.org/~sewardj/">valgrind</ulink>.
+ <ulink url="http://valgrind.org/">valgrind</ulink>.
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
- <ulink url="../debug.html#mem">Tips for memory leak hunting</ulink>
+ <link linkend="debug.memory">Tips for memory leak hunting</link>
first.
</para>
</answer>
<answer id="a-list_size_on">
<para>
See
- the <ulink url="../23_containers/howto.html#6">Containers</ulink>
+ the <link linkend="manual.containers">Containers</link>
chapter.
</para>
</answer>
patches</ulink> 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++
- <ulink url="../17_intro/contribute.html">contributors' page</ulink>
+ <link linkend="appendix.contrib">contributors' page</link>
also talks about how to submit patches.
</para>
<para>
The copy will take O(n) time and the swap is constant time.
</para>
<para>
- See <ulink url="../21_strings/howto.html#6">Shrink-to-fit
- strings</ulink> for a similar solution for strings.
+ See <link linkend="strings.string.shrink">Shrink-to-fit
+ strings</link> for a similar solution for strings.
</para>
</answer>
</qandaentry>
<para>
To use the libstdc++ parallel mode, compile your application with
the compiler flag <constant>-D_GLIBCXX_PARALLEL -fopenmp</constant>. This
- will link in <code>libgomp</code>, the GNU OpenMP <ulink url="http://gcc.gnu.org/onlinedocs/libgomp">implementation</ulink>,
+ will link in <code>libgomp</code>, the GNU OpenMP <ulink url="http://gcc.gnu.org/onlinedocs/libgomp/">implementation</ulink>,
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
projects / gcc.git / commitdiff