Clarify mt_allocator documentation w.r.t deallocation

	* doc/xml/manual/mt_allocator.xml: Clarify deallocation behaviour.
	* doc/html/*: Regenerate.

From-SVN: r247742

diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index 7e39c09..b5a6719 100644 (file)
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,8 @@
+2017-05-08  Jonathan Wakely  <jwakely@redhat.com>
+
+       * doc/xml/manual/mt_allocator.xml: Clarify deallocation behaviour.
+       * doc/html/*: Regenerate.
+
 2017-05-02  Hugo Beauzée-Luyssen <hugo@beauzee.fr>
 
        PR libstdc++/69506

diff --git a/libstdc++-v3/doc/html/manual/mt_allocator_impl.html b/libstdc++-v3/doc/html/manual/mt_allocator_impl.html
index 7b3379a..206d1a8 100644 (file)
--- a/libstdc++-v3/doc/html/manual/mt_allocator_impl.html
+++ b/libstdc++-v3/doc/html/manual/mt_allocator_impl.html
@@ -131,7 +131,8 @@ The _S_initialize() function:
     are grabbed from the global list to a thread specific list or when
     a thread decides to return some blocks to the global freelist.
 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="allocator.mt.deallocation"></a>Deallocation Notes</h3></div></div></div><p> Notes about deallocation. This allocator does not explicitly
-release memory. Because of this, memory debugging programs like
+release memory back to the OS, but keeps its own freelists instead.
+Because of this, memory debugging programs like
 valgrind or purify may notice leaks: sorry about this
 inconvenience. Operating systems will reclaim allocated memory at
 program termination anyway. If sidestepping this kind of noise is

diff --git a/libstdc++-v3/doc/xml/manual/mt_allocator.xml b/libstdc++-v3/doc/xml/manual/mt_allocator.xml
index 12fe2ee..3254bf8 100644 (file)
--- a/libstdc++-v3/doc/xml/manual/mt_allocator.xml
+++ b/libstdc++-v3/doc/xml/manual/mt_allocator.xml
@@ -281,7 +281,8 @@ The _S_initialize() function:
 
 
 <para> Notes about deallocation. This allocator does not explicitly
-release memory. Because of this, memory debugging programs like
+release memory back to the OS, but keeps its own freelists instead.
+Because of this, memory debugging programs like
 valgrind or purify may notice leaks: sorry about this
 inconvenience. Operating systems will reclaim allocated memory at
 program termination anyway. If sidestepping this kind of noise is