From e41b988cc5af34e9c1a3d37b717fbfcc52d7ff90 Mon Sep 17 00:00:00 2001
From: Gerald Pfeifer <gerald@pfeifer.com>
Date: Mon, 1 Jun 2020 17:03:51 +0200
Subject: [PATCH] libstdc++: Update/streamline Valgrind references

	* doc/xml/faq.xml: Adjust Valgrind reference and remove another.
	* doc/html/faq.html: Regenerate.
---
 libstdc++-v3/doc/html/faq.html | 4 ++--
 libstdc++-v3/doc/xml/faq.xml   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html
index 18407225d7a..967e5f5f348 100644
--- a/libstdc++-v3/doc/html/faq.html
+++ b/libstdc++-v3/doc/html/faq.html
@@ -700,7 +700,7 @@
     of a few dozen kilobytes on startup. This pool is used to ensure it's
     possible to throw exceptions (such as <code class="classname">bad_alloc</code>)
     even when <code class="code">malloc</code> is unable to allocate any more memory.
-    With some versions of <a class="link" href="http://valgrind.org/" target="_top"><span class="command"><strong>valgrind</strong></span></a>
+    With some versions of <a class="link" href="https://valgrind.org" target="_top"><span class="command"><strong>valgrind</strong></span></a>
     this pool will be shown as "still reachable" when the process exits, e.g.
     <code class="code">still reachable: 72,704 bytes in 1 blocks</code>.
     This memory is not a leak, because it's still in use by libstdc++,
@@ -710,7 +710,7 @@
     </p><p>
     In the past, a few people reported that the standard containers appear
     to leak memory when tested with memory checkers such as
-    <a class="link" href="http://valgrind.org/" target="_top"><span class="command"><strong>valgrind</strong></span></a>.
+    <span class="command"><strong>valgrind</strong></span>.
     Under some (non-default) configurations the library's allocators keep
     free memory in a
     pool for later reuse, rather than deallocating it with <code class="code">delete</code>
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index cf8684e1cea..e419d3c22a0 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -993,7 +993,7 @@
     of a few dozen kilobytes on startup. This pool is used to ensure it's
     possible to throw exceptions (such as <classname>bad_alloc</classname>)
     even when <code>malloc</code> is unable to allocate any more memory.
-    With some versions of <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://valgrind.org/"><command>valgrind</command></link>
+    With some versions of <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://valgrind.org"><command>valgrind</command></link>
     this pool will be shown as "still reachable" when the process exits, e.g.
     <code>still reachable: 72,704 bytes in 1 blocks</code>.
     This memory is not a leak, because it's still in use by libstdc++,
@@ -1004,7 +1004,7 @@
     <para>
     In the past, a few people reported that the standard containers appear
     to leak memory when tested with memory checkers such as
-    <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://valgrind.org/"><command>valgrind</command></link>.
+    <command>valgrind</command>.
     Under some (non-default) configurations the library's allocators keep
     free memory in a
     pool for later reuse, rather than deallocating it with <code>delete</code>