diff options
| author | ljrittle <ljrittle@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-06-08 03:53:35 +0000 |
|---|---|---|
| committer | ljrittle <ljrittle@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-06-08 03:53:35 +0000 |
| commit | 6e77e3236833da984422d1c758e9d3188d9925c7 (patch) | |
| tree | b2cbfba3edc6eab1c6b67a4c3000514516e6ca14 /libstdc++-v3/docs | |
| parent | ff09141288889ce509849b1ce77b549f23b54831 (diff) | |
| download | gcc-6e77e3236833da984422d1c758e9d3188d9925c7.tar.gz | |
* config/threads-no.h: Remove file.
* config/threads-posix.h: Remove file.
* acconfig.h (_GLIBCPP_USE_THREADS): Remove.
(_GLIBCPP_SUPPORTS_WEAK): Add (required by namespace-clean gthr*.h).
(_GLIBCPP_HAVE_GTHR_DEFAULT): Likewise.
* config.h.in: Regenerate.
* acinclude.m4 (GLIBCPP_ENABLE_THREADS): Completely rework to
setup and use gthr*.h files. In particular, make gthr.h files
namespace-clean in the staging area (they don't have to be for
libgcc.a).
* aclocal.m4: Regenerate.
* configure: Regenerate.
* src/Makefile.am (build_headers): Remove bits/c++threads.h
and add bits/gthr.h bits/gthr-single.h bits/gthr-default.h.
* src/Makefile.in: Regenerate.
* include/bits/c++config: Cleanup threading configuration macros.
In particular, define __STL_GTHREADS macro which controls...
* include/bits/stl_threads.h: ...a brand new gthr.h-based
configuration here.
* config/c_io_stdio.h: Include staged gthr.h instead of local
thread configuration file. Always use __gthread_mutex_t
instead of __mutext_type (or int).
* include/bits/std_fstream.h: Likewise.
* docs/html/17_intro/howto.html: Remove placeholder comment in
case this configuration patch didn't make it. Add advice that
section only applies if configured with --enable-threads.
* docs/html/23_containers/howto.html: Reword to make clear
that _PTHREADS is no longer required for any port to be
correctly using STL with threads. Add advice that section
only applies if configured with --enable-threads.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@42998 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'libstdc++-v3/docs')
| -rw-r--r-- | libstdc++-v3/docs/html/17_intro/howto.html | 21 | ||||
| -rw-r--r-- | libstdc++-v3/docs/html/23_containers/howto.html | 9 |
2 files changed, 10 insertions, 20 deletions
diff --git a/libstdc++-v3/docs/html/17_intro/howto.html b/libstdc++-v3/docs/html/17_intro/howto.html index 3b1cf13d6c4..34779e40fa8 100644 --- a/libstdc++-v3/docs/html/17_intro/howto.html +++ b/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.4 2001/05/30 21:54:57 pme Exp $ --> +<!-- $Id: howto.html,v 1.5 2001/05/31 02:45:03 ljrittle Exp $ --> </HEAD> <BODY> @@ -57,7 +57,8 @@ 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 thread-safe containers will be - in section 6.8 (the HOWTOs on containers). + in section 6.8 (the HOWTOs on containers). This section only applies + when gcc and libstdc++-v3 were configured with --enable-threads. </P> <P>The libstdc++ code (all of it, not just the containers) has been designed so that thread-safety will be easily possible. The first @@ -79,19 +80,7 @@ in include/bits/c++config and the HOWTOs on containers. Be fully aware that you may change the external or internal ABI of libstdc++-v3 when you provide -D__USE_MALLOC on the command line - or make a change to that configuration file. [Placeholder in - case other patches don't make it before the 3.0 release: That - memory allocator can appear buggy in multithreaded C++ programs - (and has been reported to leak memory), if STL is misconfigured - for your platform. You may need to provide -D_PTHREADS on the - command line in this case to ensure the memory allocator for - containers is really protected by a mutex. Also, be aware that - you just changed the ABI of libstdc++-v3 when you did that thus - your entire application and all libraries must be compiled with - compatible flags. The STL implementation doesn't currently - protect you from changing the mutex locking implementation to - one that doesn't really play together with the implementation - you may have compiled other application code with.] + or make a change to that configuration file. </P> <P> If you don't like caches of objects being retained inside the @@ -192,7 +181,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.4 2001/05/30 21:54:57 pme Exp $ +<BR> $Id: howto.html,v 1.5 2001/05/31 02:45:03 ljrittle Exp $ </EM></P> diff --git a/libstdc++-v3/docs/html/23_containers/howto.html b/libstdc++-v3/docs/html/23_containers/howto.html index bc05128bd99..6f20c9b1d8a 100644 --- a/libstdc++-v3/docs/html/23_containers/howto.html +++ b/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.4 2001/05/30 21:55:01 pme Exp $ --> +<!-- $Id: howto.html,v 1.5 2001/05/31 02:45:02 ljrittle Exp $ --> </HEAD> <BODY> @@ -185,7 +185,8 @@ <P>This section will mention some of the problems in designing MT programs that use Standard containers. For information on other aspects of multithreading (e.g., the library as a whole), see - the Received Wisdom on Chapter 17. + the Received Wisdom on Chapter 17. This section only applies + when gcc and libstdc++-v3 were configured with --enable-threads. </P> <P>Two excellent pages to read when working with templatized containers and threads are @@ -207,7 +208,7 @@ the mutex lock as is best for your platform. In particular, past advice was for people using g++ to explicitly define _PTHREADS on the command line to get a thread-safe STL. This - may or may not be required for your port. It may or may not be + is no longer required for your port. It may or may not be a good idea for your port. Extremely big caution: if you compile some of your application code against the STL with one set of threading flags and macros and another portion of the @@ -258,7 +259,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.4 2001/05/30 21:55:01 pme Exp $ +<BR> $Id: howto.html,v 1.5 2001/05/31 02:45:02 ljrittle Exp $ </EM></P> |