Skip to content

R
riscv-gcc-1
Commit b86ee4a5 by Loren J. Rittle Committed by Loren J. Rittle
Options

howto.html: Update link. 

	* docs/html/17_intro/howto.html: Update link.
	* docs/html/23_containers/howto.html: Likewise.  Add new link.

From-SVN: r42703
parent 8df506da
Showing with 19 additions and 11 deletions
libstdc++-v3/ChangeLog
2001-05-30 Loren J. Rittle <ljrittle@acm.org>
* docs/html/17_intro/howto.html: Update link.
* docs/html/23_containers/howto.html: Likewise. Add new link.
2001-05-26 Gabriel Dos Reis <gdr@codesourcery.com>
* include/c_std/bits/std_cmath.h (sqrt): #undef.
......
libstdc++-v3/docs/html/17_intro/howto.html
......@@ -8,7 +8,7 @@
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 17</TITLE>
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.1 2000/12/10 04:03:09 pme Exp $ -->
<!-- $Id: howto.html,v 1.2 2001/04/03 00:26:54 pme Exp $ -->
</HEAD>
<BODY>
......@@ -56,7 +56,7 @@
and gcc mailing lists on a regular basis (probably by a cron job).
This entry will mention a very little bit about the general MT
issues with libstdc++. The latest status and quick notes will be
in FAQ 5.6. Some discussion about threadsafe containers will be
in FAQ 5.6. Some discussion about thread-safe containers will be
in section 6.8 (the HOWTOs on containers).
</P>
<P>The libstdc++ code (all of it, not just the containers) has been
......@@ -65,7 +65,7 @@
portable to all platforms. A minor problem that pops up every so
often is different interpretations of what &quot;thread-safe&quot;
means for a library (not a general program). We currently use the
<A HREF="http://www.sgi.com/Technology/STL/thread_safety.html">same
<A HREF="http://www.sgi.com/tech/stl/thread_safety.html">same
definition that SGI</A> uses for their STL subset.
</P>
<P>A recent journal article has described &quot;atomic integer
......@@ -145,7 +145,7 @@
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:libstdc++@gcc.gnu.org">the mailing list</A>.
<BR> $Id: howto.html,v 1.1 2000/12/10 04:03:09 pme Exp $
<BR> $Id: howto.html,v 1.2 2001/04/03 00:26:54 pme Exp $
</EM></P>
......
libstdc++-v3/docs/html/23_containers/howto.html
......@@ -8,7 +8,7 @@
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 23</TITLE>
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.1 2000/12/10 04:04:55 pme Exp $ -->
<!-- $Id: howto.html,v 1.2 2001/04/03 00:26:55 pme Exp $ -->
</HEAD>
<BODY>
......@@ -189,13 +189,16 @@
aspects of multithreading (e.g., the library as a whole), see
the Received Wisdom on Chapter 17.
</P>
<P>An excellent page to read when working with templatized containers
and threads is
<A HREF="http://www.sgi.com/Technology/STL/thread_safety.html">SGI's
http://www.sgi.com/Technology/STL/thread_safety.html</A>. The
<P>Two excellent pages to read when working with templatized containers
and threads are
<A HREF="http://www.sgi.com/tech/stl/thread_safety.html">SGI's
http://www.sgi.com/tech/stl/thread_safety.html</A> and
<A HREF="http://www.sgi.com/tech/stl/Allocators.html">SGI's
http://www.sgi.com/tech/stl/Allocators.html</A>. The
libstdc++-v3 uses the same definition of thread safety
when discussing design. A key point that beginners may miss is the
fourth major paragraph (&quot;For most clients,&quot;...), pointing
fourth major paragraph of the first page mentioned above
(&quot;For most clients,&quot;...), pointing
out that locking must nearly always be done outside the container,
by client code (that'd be you, not us *grin*).
</P>
......@@ -236,7 +239,7 @@
<P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:libstdc++@gcc.gnu.org">the mailing list</A>.
<BR> $Id: howto.html,v 1.1 2000/12/10 04:04:55 pme Exp $
<BR> $Id: howto.html,v 1.2 2001/04/03 00:26:55 pme Exp $
</EM></P>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment