Update libstdc++ API Evolution documentation

	* doc/xml/manual/allocator.xml: Link to table documenting evolution
	of extension allocators.
	* doc/xml/manual/evolution.xml: Use angle brackets for header names.
	Document new headers in 7.2, 8.1 and 9.1 releases.
	* doc/xml/manual/using.xml: Adjust link target for new_allocator.
	* doc/html/*: Regenerate.

From-SVN: r269794

libstdc++-v3/ChangeLog

+2019-03-19  Jonathan Wakely  <jwakely@redhat.com>
+
+	* doc/xml/manual/allocator.xml: Link to table documenting evolution
+	of extension allocators.
+	* doc/xml/manual/evolution.xml: Use angle brackets for header names.
+	Document new headers in 7.2, 8.1 and 9.1 releases.
+	* doc/xml/manual/using.xml: Adjust link target for new_allocator.
+	* doc/html/*: Regenerate.
+
 2019-03-12  John David Anglin  <dave.anglin@bell.net>
 
 	PR libstdc++/89461

libstdc++-v3/doc/html/manual/memory.html

@@ -204,8 +204,8 @@
     names have changed, but in all cases, functionality is
     equivalent. Starting with gcc-3.4, all extension allocators are
     standard style. Before this point, SGI style was the norm. Because of
-    this, the number of template arguments also changed. Here's a simple
-    chart to track the changes.
+    this, the number of template arguments also changed.
+    <a class="xref" href="api.html#table.extension_allocators" title="Table B.6. Extension Allocators">Table B.6, “Extension Allocators”</a> tracks the changes.
   </p><p>
     More details on each of these extension allocators follows.
   </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>

libstdc++-v3/doc/html/manual/using_macros.html

@@ -116,7 +116,7 @@
         enabled for
         <code class="classname">std::vector&lt;T, std::allocator&lt;T&gt;&gt;</code>
         and only when <code class="classname">std::allocator</code> is derived from
-        <a class="link" href="memory.html#allocator.impl" title="Implementation"><code class="classname">new_allocator</code>
+        <a class="link" href="memory.html#allocator.ext" title="Extension Allocators"><code class="classname">new_allocator</code>
         or <code class="classname">malloc_allocator</code></a>. The annotations
         must be present on all vector operations or none, so this macro must
         be defined to the same value for all translation units that create,

libstdc++-v3/doc/xml/manual/allocator.xml

@@ -139,7 +139,6 @@
 
   <section xml:id="allocator.interface"><info><title>Interface Design</title></info>
 
-
    <para>
      The only allocator interface that
      is supported is the standard C++ interface. As such, all STL
@@ -163,7 +162,6 @@
 
   <section xml:id="allocator.default"><info><title>Selecting Default Allocation Policy</title></info>
 
-
    <para>
      It's difficult to pick an allocation strategy that will provide
    maximum utility, without excessively penalizing some behavior. In
@@ -229,7 +227,6 @@
 
   <section xml:id="allocator.caching"><info><title>Disabling Memory Caching</title></info>
 
-
     <para>
       In use, <classname>allocator</classname> may allocate and
       deallocate using implementation-specific strategies and
@@ -328,8 +325,8 @@
     names have changed, but in all cases, functionality is
     equivalent. Starting with gcc-3.4, all extension allocators are
     standard style. Before this point, SGI style was the norm. Because of
-    this, the number of template arguments also changed. Here's a simple
-    chart to track the changes.
+    this, the number of template arguments also changed.
+    <xref linkend="table.extension_allocators"/> tracks the changes.
   </para>
 
   <para>

libstdc++-v3/doc/xml/manual/using.xml

@@ -1192,7 +1192,7 @@ g++ -Winvalid-pch -I. -include stdc++.h -H -g -O2 hello.cc -o test.exe
         enabled for
         <classname>std::vector&lt;T, std::allocator&lt;T&gt;&gt;</classname>
         and only when <classname>std::allocator</classname> is derived from
-        <link linkend="allocator.impl"><classname>new_allocator</classname>
+        <link linkend="allocator.ext"><classname>new_allocator</classname>
         or <classname>malloc_allocator</classname></link>. The annotations
         must be present on all vector operations or none, so this macro must
         be defined to the same value for all translation units that create,