From: Jonathan Wakely Date: Thu, 11 May 2017 15:01:10 +0000 (+0100) Subject: Fix ViewCVS URLs in libstdc++ manual X-Git-Tag: basepoints/gcc-9~7385 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=395ec8f30c029921849c760547b2a7dc9b333088;p=thirdparty%2Fgcc.git Fix ViewCVS URLs in libstdc++ manual * doc/xml/manual/allocator.xml: Fix ViewCVS URLs. * doc/xml/manual/mt_allocator.xml: Likewise. * doc/html/*: Regenerate. From-SVN: r247911 --- diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 298d35182e67..5d69a8edac45 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,5 +1,9 @@ 2017-05-11 Jonathan Wakely + * doc/xml/manual/allocator.xml: Fix ViewCVS URLs. + * doc/xml/manual/mt_allocator.xml: Likewise. + * doc/html/*: Regenerate. + PR libstdc++/80285 * include/bits/shared_ptr_base.h (_Sp_make_shared_tag::_S_ti): Define function to get unique fake std::type_info reference. diff --git a/libstdc++-v3/doc/html/manual/memory.html b/libstdc++-v3/doc/html/manual/memory.html index d310b6954719..2dfa4a21e411 100644 --- a/libstdc++-v3/doc/html/manual/memory.html +++ b/libstdc++-v3/doc/html/manual/memory.html @@ -119,8 +119,8 @@ Over multiple iterations, various STL container objects have elements inserted to some maximum amount. A variety of allocators are tested. - Test source for sequence - and associative + Test source for sequence + and associative containers.

  • Insertion and erasure in a multi-threaded environment. @@ -129,14 +129,14 @@ on a per-thread basis, as well as measuring thread contention for memory resources. Test source - here. + here.

  • A threaded producer/consumer model.

    Test source for - sequence + sequence and - associative + associative containers.

    • The current default choice for diff --git a/libstdc++-v3/doc/html/manual/mt_allocator_impl.html b/libstdc++-v3/doc/html/manual/mt_allocator_impl.html index 206d1a806ae4..7c1d020c2017 100644 --- a/libstdc++-v3/doc/html/manual/mt_allocator_impl.html +++ b/libstdc++-v3/doc/html/manual/mt_allocator_impl.html @@ -156,6 +156,6 @@ containers, this works, as an instance of the allocator is constructed as part of a container's constructor. However, this assumption is implementation-specific, and subject to change. For an example of a pool that frees memory, see the following - + example.

    Prev Up Next
    Design Issues Home Single Thread Example
    \ No newline at end of file diff --git a/libstdc++-v3/doc/xml/manual/allocator.xml b/libstdc++-v3/doc/xml/manual/allocator.xml index 3aaad338adef..395b4e3b4ba3 100644 --- a/libstdc++-v3/doc/xml/manual/allocator.xml +++ b/libstdc++-v3/doc/xml/manual/allocator.xml @@ -185,8 +185,8 @@ Over multiple iterations, various STL container objects have elements inserted to some maximum amount. A variety of allocators are tested. - Test source for sequence - and associative + Test source for sequence + and associative containers. @@ -201,7 +201,7 @@ on a per-thread basis, as well as measuring thread contention for memory resources. Test source - here. + here. @@ -211,9 +211,9 @@ Test source for - sequence + sequence and - associative + associative containers. diff --git a/libstdc++-v3/doc/xml/manual/mt_allocator.xml b/libstdc++-v3/doc/xml/manual/mt_allocator.xml index 3254bf88d2c0..e89a0145490d 100644 --- a/libstdc++-v3/doc/xml/manual/mt_allocator.xml +++ b/libstdc++-v3/doc/xml/manual/mt_allocator.xml @@ -308,7 +308,7 @@ containers, this works, as an instance of the allocator is constructed as part of a container's constructor. However, this assumption is implementation-specific, and subject to change. For an example of a pool that frees memory, see the following - + example.