The GNU C++ Library

Short Contents

The GNU C++ Library
Â	Â	Â Next

The GNU C++ Library

Short Contents

diff --git a/libstdc++-v3/doc/html/manual/abi.html b/libstdc++-v3/doc/html/manual/abi.html index 0eb6a12a5011..8dab47dbb933 100644 --- a/libstdc++-v3/doc/html/manual/abi.html +++ b/libstdc++-v3/doc/html/manual/abi.html @@ -28,7 +28,7 @@ g++ command line options may change the ABI as a side-effect of use. Such flags include -fpack-struct and -fno-exceptions, but include others: see the complete - list in the GCC manual under the heading Options + list in the GCC manual under the heading Options for Code Generation Conventions.

The configure options used when building a specific libstdc++ diff --git a/libstdc++-v3/doc/html/manual/ext_concurrency_impl.html b/libstdc++-v3/doc/html/manual/ext_concurrency_impl.html index 23b90f34572b..669c07cf2917 100644 --- a/libstdc++-v3/doc/html/manual/ext_concurrency_impl.html +++ b/libstdc++-v3/doc/html/manual/ext_concurrency_impl.html @@ -34,7 +34,7 @@ non-ancient x86 hardware, -march=native usually does t trick.

For hosts without compiler intrinsics, but with capable hardware, hand-crafted assembly is selected. This is the case for the following hosts:

cris
hppa
i386
i486
m48k
mips
sparc

And for the rest, a simulated atomic lock via pthreads. -

Detailed information about compiler intrinsics for atomic operations can be found in the GCC documentation. +

Detailed information about compiler intrinsics for atomic operations can be found in the GCC documentation.

More details on the library fallbacks from the porting section.

Thread Abstraction

A thin layer above IEEE 1003.1 (i.e. pthreads) is used to abstract the thread interface for GCC. This layer is called "gthread," and is @@ -44,7 +44,7 @@ a POSIX-like interface. the current host. In libstdc++ implementation files, <bits/gthr.h> is used to select the proper gthreads file.

Within libstdc++ sources, all calls to underlying thread functionality -use this layer. More detail as to the specific interface can be found in the source documentation. +use this layer. More detail as to the specific interface can be found in the source documentation.

By design, the gthread layer is interoperable with the types, functions, and usage found in the usual <pthread.h> file, including pthread_t, pthread_once_t, pthread_create, diff --git a/libstdc++-v3/doc/html/manual/ext_demangling.html b/libstdc++-v3/doc/html/manual/ext_demangling.html index b5fb87b91c5d..1eae99a1859b 100644 --- a/libstdc++-v3/doc/html/manual/ext_demangling.html +++ b/libstdc++-v3/doc/html/manual/ext_demangling.html @@ -7,7 +7,7 @@ original C++ source identifiers is called âdemangling.â

- If you have read the source + If you have read the source documentation for namespace abi then you are aware of the cross-vendor C++ ABI in use by GCC. One of the exposed functions is used for demangling, diff --git a/libstdc++-v3/doc/html/manual/memory.html b/libstdc++-v3/doc/html/manual/memory.html index 3a2025b90d26..aca90892bdad 100644 --- a/libstdc++-v3/doc/html/manual/memory.html +++ b/libstdc++-v3/doc/html/manual/memory.html @@ -525,7 +525,7 @@ available policies are: _S_atomic

Selected when GCC supports a builtin atomic compare-and-swap operation -on the target processor (see Atomic +on the target processor (see Atomic Builtins.) The reference counts are maintained using a lock-free algorithm and GCC's atomic builtins, which provide the required memory synchronisation. diff --git a/libstdc++-v3/doc/html/manual/parallel_mode_design.html b/libstdc++-v3/doc/html/manual/parallel_mode_design.html index 1d5cbbc99d9f..c2090940d249 100644 --- a/libstdc++-v3/doc/html/manual/parallel_mode_design.html +++ b/libstdc++-v3/doc/html/manual/parallel_mode_design.html @@ -174,7 +174,7 @@ i. e. it is a singleton. It can be read and written by calling __gnu_parallel::_Settings::set, respectively. Please note that the first call return a const object, so direct manipulation is forbidden. -See +See <parallel/settings.h> for complete details.

diff --git a/libstdc++-v3/doc/html/manual/parallel_mode_using.html b/libstdc++-v3/doc/html/manual/parallel_mode_using.html index 1f151f4ed7b7..38d629fe74fd 100644 --- a/libstdc++-v3/doc/html/manual/parallel_mode_using.html +++ b/libstdc++-v3/doc/html/manual/parallel_mode_using.html @@ -5,7 +5,7 @@ not difficult: just compile your application with the compiler flag -fopenmp. This will link in libgomp, the - GNU Offloading and + GNU Offloading and Multi Processing Runtime Library, whose presence is mandatory.

diff --git a/libstdc++-v3/doc/html/manual/using_exceptions.html b/libstdc++-v3/doc/html/manual/using_exceptions.html index e5ef8be3a42c..706b27e14793 100644 --- a/libstdc++-v3/doc/html/manual/using_exceptions.html +++ b/libstdc++-v3/doc/html/manual/using_exceptions.html @@ -166,8 +166,8 @@ exception neutrality and exception safety. implicitly generated magic necessary to support try and catch blocks and thrown objects. (Language support - for -fno-exceptions is documented in the GNU - GCC manual.) + for -fno-exceptions is documented in the GCC + manual.)

Before detailing the library support for -fno-exceptions, first a passing note on the things lost when this flag is used: it will break exceptions diff --git a/libstdc++-v3/doc/xml/manual/abi.xml b/libstdc++-v3/doc/xml/manual/abi.xml index a4ce866b8843..15954ae880d9 100644 --- a/libstdc++-v3/doc/xml/manual/abi.xml +++ b/libstdc++-v3/doc/xml/manual/abi.xml @@ -52,7 +52,7 @@ g++ command line options may change the ABI as a side-effect of use. Such flags include -fpack-struct and -fno-exceptions, but include others: see the complete - list in the GCC manual under the heading Options + list in the GCC manual under the heading Options for Code Generation Conventions. diff --git a/libstdc++-v3/doc/xml/manual/concurrency_extensions.xml b/libstdc++-v3/doc/xml/manual/concurrency_extensions.xml index 6499fda58c38..e845431818ba 100644 --- a/libstdc++-v3/doc/xml/manual/concurrency_extensions.xml +++ b/libstdc++-v3/doc/xml/manual/concurrency_extensions.xml @@ -267,7 +267,7 @@ hardware, hand-crafted assembly is selected. This is the case for the following And for the rest, a simulated atomic lock via pthreads. - Detailed information about compiler intrinsics for atomic operations can be found in the GCC documentation. +Detailed information about compiler intrinsics for atomic operations can be found in the GCC documentation. More details on the library fallbacks from the porting section. @@ -290,7 +290,7 @@ the current host. In libstdc++ implementation files, Within libstdc++ sources, all calls to underlying thread functionality -use this layer. More detail as to the specific interface can be found in the source documentation. +use this layer. More detail as to the specific interface can be found in the source documentation. By design, the gthread layer is interoperable with the types, diff --git a/libstdc++-v3/doc/xml/manual/extensions.xml b/libstdc++-v3/doc/xml/manual/extensions.xml index 490a50cc3317..d0460b0d90c0 100644 --- a/libstdc++-v3/doc/xml/manual/extensions.xml +++ b/libstdc++-v3/doc/xml/manual/extensions.xml @@ -504,7 +504,7 @@ get_temporary_buffer(5, (int*)0); demangling. - If you have read the source + If you have read the source documentation for namespace abi then you are aware of the cross-vendor C++ ABI in use by GCC. One of the exposed functions is used for demangling, diff --git a/libstdc++-v3/doc/xml/manual/parallel_mode.xml b/libstdc++-v3/doc/xml/manual/parallel_mode.xml index cabb9d76a4cf..22f432f762cd 100644 --- a/libstdc++-v3/doc/xml/manual/parallel_mode.xml +++ b/libstdc++-v3/doc/xml/manual/parallel_mode.xml @@ -121,7 +121,7 @@ It might work with other compilers, though. flag -fopenmp. This will link in libgomp, the GNU Offloading and + xlink:href="https://gcc.gnu.org/onlinedocs/libgomp/">GNU Offloading and Multi Processing Runtime Library, whose presence is mandatory. @@ -739,7 +739,7 @@ i. e. it is a singleton. It can be read and written by calling __gnu_parallel::_Settings::set, respectively. Please note that the first call return a const object, so direct manipulation is forbidden. -See +See <parallel/settings.h> for complete details. diff --git a/libstdc++-v3/doc/xml/manual/shared_ptr.xml b/libstdc++-v3/doc/xml/manual/shared_ptr.xml index 07cc4d527152..3d59a04c5041 100644 --- a/libstdc++-v3/doc/xml/manual/shared_ptr.xml +++ b/libstdc++-v3/doc/xml/manual/shared_ptr.xml @@ -243,7 +243,7 @@ available policies are: Selected when GCC supports a builtin atomic compare-and-swap operation -on the target processor (see Atomic +on the target processor (see Atomic Builtins.) The reference counts are maintained using a lock-free algorithm and GCC's atomic builtins, which provide the required memory synchronisation. diff --git a/libstdc++-v3/doc/xml/manual/using_exceptions.xml b/libstdc++-v3/doc/xml/manual/using_exceptions.xml index b7a0cc084976..ab42c8099399 100644 --- a/libstdc++-v3/doc/xml/manual/using_exceptions.xml +++ b/libstdc++-v3/doc/xml/manual/using_exceptions.xml @@ -282,8 +282,8 @@ exception neutrality and exception safety. implicitly generated magic necessary to support try and catch blocks and thrown objects. (Language support - for -fno-exceptions is documented in the GNU - GCC manual.) + for -fno-exceptions is documented in the GCC + manual.) Before detailing the library support