https://gcc.gnu.org/g:409e766bea64027da3442c30c29799d37f802733

commit r14-11161-g409e766bea64027da3442c30c29799d37f802733
Author: Gerald Pfeifer <ger...@pfeifer.com>
Date:   Sat Aug 17 15:21:21 2024 +0200

    libstdc++: Update references to gcc.gnu.org/onlinedocs
    
    libstdc++-v3:
            * doc/xml/manual/abi.xml: Update reference to
            gcc.gnu.org/onlinedocs.
            * doc/xml/manual/concurrency_extensions.xml (interface): Ditto.
            * doc/xml/manual/extensions.xml: Ditto.
            * doc/xml/manual/parallel_mode.xml: Ditto.
            * doc/xml/manual/shared_ptr.xml: Ditto.
            * doc/xml/manual/using_exceptions.xml: Ditto. And change GNU GCC
            to GCC.
            * doc/html/index.html: Regenerate.
            * doc/html/manual/abi.html: Ditto.
            * doc/html/manual/ext_concurrency_impl.html: Ditto.
            * doc/html/manual/ext_demangling.html: Ditto.
            * doc/html/manual/memory.html: Ditto.
            * doc/html/manual/parallel_mode_design.html: Ditto.
            * doc/html/manual/parallel_mode_using.html: Ditto.
            * doc/html/manual/using_exceptions.html: Ditto.
    
    (cherry picked from commit e68ab0f16072af97f0898fa0a14e72fcda442775)

Diff:
---
 libstdc++-v3/doc/html/index.html                       | 4 ++--
 libstdc++-v3/doc/html/manual/abi.html                  | 2 +-
 libstdc++-v3/doc/html/manual/ext_concurrency_impl.html | 4 ++--
 libstdc++-v3/doc/html/manual/ext_demangling.html       | 2 +-
 libstdc++-v3/doc/html/manual/memory.html               | 2 +-
 libstdc++-v3/doc/html/manual/parallel_mode_design.html | 2 +-
 libstdc++-v3/doc/html/manual/parallel_mode_using.html  | 2 +-
 libstdc++-v3/doc/html/manual/using_exceptions.html     | 4 ++--
 libstdc++-v3/doc/xml/manual/abi.xml                    | 2 +-
 libstdc++-v3/doc/xml/manual/concurrency_extensions.xml | 4 ++--
 libstdc++-v3/doc/xml/manual/extensions.xml             | 2 +-
 libstdc++-v3/doc/xml/manual/parallel_mode.xml          | 4 ++--
 libstdc++-v3/doc/xml/manual/shared_ptr.xml             | 2 +-
 libstdc++-v3/doc/xml/manual/using_exceptions.xml       | 4 ++--
 14 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/libstdc++-v3/doc/html/index.html b/libstdc++-v3/doc/html/index.html
index 88ef88412669..395908f17a1a 100644
--- a/libstdc++-v3/doc/html/index.html
+++ b/libstdc++-v3/doc/html/index.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";><html 
xmlns="http://www.w3.org/1999/xhtml";><head><meta http-equiv="Content-Type" 
content="text/html; charset=UTF-8" /><title>The GNU C++ Library</title><meta 
name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><meta 
name="description" content="Short Contents Copyright (C) 2008-2025 FSF 
Permission is granted to copy, distribute and/or modify this document under the 
terms of the GNU Free Documentation License, Version 1.2 or any later version 
published by the Free Software Foundation; with no Invariant Sections, with no 
Front-Cover Texts, and with no Back-Cover Texts. This is the top level of the 
libstdc++ documentation set. The documentation is divided into the following 
three sections. Manual Frequently Asked Questions API and Source Documentation" 
/><meta name="keywords" content="ISO C++, runtime, library" /><link rel="home" 
href="index.html" title="Th
 e GNU C++ Library" /><link rel="next" href="manual/index.html" title="The GNU 
C++ Library Manual" /></head><body><div class="navheader"><table width="100%" 
summary="Navigation header"><tr><th colspan="3" align="center">The GNU C++ 
Library</th></tr><tr><td width="20%" align="left"> </td><th width="60%" 
align="center"> </th><td width="20%" align="right"> <a accesskey="n" 
href="manual/index.html">Next</a></td></tr></table><hr /></div><div class="set" 
lang="en" xml:lang="en"><div class="titlepage"><div><div><h1 class="title"><a 
id="set-index"></a>The GNU C++ Library</h1></div><div><div class="abstract"><a 
id="contents"></a><p class="title"><strong>Short Contents</strong></p><p>
-      Copyright (C) 2008-2025
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";><html 
xmlns="http://www.w3.org/1999/xhtml";><head><meta http-equiv="Content-Type" 
content="text/html; charset=UTF-8" /><title>The GNU C++ Library</title><meta 
name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><meta 
name="description" content="Short Contents Copyright (C) 2008-2024 FSF 
Permission is granted to copy, distribute and/or modify this document under the 
terms of the GNU Free Documentation License, Version 1.2 or any later version 
published by the Free Software Foundation; with no Invariant Sections, with no 
Front-Cover Texts, and with no Back-Cover Texts. This is the top level of the 
libstdc++ documentation set. The documentation is divided into the following 
three sections. Manual Frequently Asked Questions API and Source Documentation" 
/><meta name="keywords" content="ISO C++, runtime, library" /><link rel="home" 
href="index.html" title="Th
 e GNU C++ Library" /><link rel="next" href="manual/index.html" title="The GNU 
C++ Library Manual" /></head><body><div class="navheader"><table width="100%" 
summary="Navigation header"><tr><th colspan="3" align="center">The GNU C++ 
Library</th></tr><tr><td width="20%" align="left"> </td><th width="60%" 
align="center"> </th><td width="20%" align="right"> <a accesskey="n" 
href="manual/index.html">Next</a></td></tr></table><hr /></div><div class="set" 
lang="en" xml:lang="en"><div class="titlepage"><div><div><h1 class="title"><a 
id="set-index"></a>The GNU C++ Library</h1></div><div><div class="abstract"><a 
id="contents"></a><p class="title"><strong>Short Contents</strong></p><p>
+      Copyright (C) 2008-2024
       <a class="link" href="https://www.fsf.org"; target="_top">FSF
       </a>
     </p><p>
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 <code class="code">-fpack-struct</code> and
   <code class="code">-fno-exceptions</code>, but include others: see the 
complete
-  list in the GCC manual under the heading <a class="link" 
href="http://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#Code%20Gen%20Options";
 target="_top">Options
+  list in the GCC manual under the heading <a class="link" 
href="https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#Code%20Gen%20Options";
 target="_top">Options
   for Code Generation Conventions</a>.
 </p><p>
   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, <code 
class="code">-march=native</code> usually does t
 trick.</p><p> For hosts without compiler intrinsics, but with capable
 hardware, hand-crafted assembly is selected. This is the case for the 
following hosts:
 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: 
disc; "><li class="listitem"><p>cris</p></li><li 
class="listitem"><p>hppa</p></li><li class="listitem"><p>i386</p></li><li 
class="listitem"><p>i486</p></li><li class="listitem"><p>m48k</p></li><li 
class="listitem"><p>mips</p></li><li 
class="listitem"><p>sparc</p></li></ul></div><p>And for the rest, a simulated 
atomic lock via pthreads.
-</p><p> Detailed information about compiler intrinsics for atomic operations 
can be found in the GCC <a class="link" 
href="http://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html"; 
target="_top"> documentation</a>.
+</p><p>Detailed information about compiler intrinsics for atomic operations 
can be found in the GCC <a class="link" 
href="https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html"; 
target="_top"> documentation</a>.
 </p><p> More details on the library fallbacks from the porting <a class="link" 
href="internals.html#internals.thread_safety" title="Thread Safety">section</a>.
 </p></div><div class="section"><div class="titlepage"><div><div><h3 
class="title"><a id="manual.ext.concurrency.impl.thread"></a>Thread 
Abstraction</h3></div></div></div><p>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,
 &lt;bits/gthr.h&gt; is used to select the proper gthreads file.
 </p><p>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 <a class="link" 
href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html"; 
target="_top">documentation</a>.
+use this layer. More detail as to the specific interface can be found in the 
source <a class="link" 
href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html"; 
target="_top">documentation</a>.
 </p><p>By design, the gthread layer is interoperable with the types,
 functions, and usage found in the usual &lt;pthread.h&gt; file,
 including <code class="code">pthread_t</code>, <code 
class="code">pthread_once_t</code>, <code class="code">pthread_create</code>,
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
     <span class="quote">“<span class="quote">demangling.</span>”</span>
   </p><p>
-    If you have read the <a class="link" 
href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/namespaces.html"; 
target="_top">source
+    If you have read the <a class="link" 
href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/namespaces.html"; 
target="_top">source
     documentation for <code class="code">namespace abi</code></a> 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:
        <code class="constant">_S_atomic</code>
        </p><p>
 Selected when GCC supports a builtin atomic compare-and-swap operation
-on the target processor (see <a class="link" 
href="http://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html"; 
target="_top">Atomic
+on the target processor (see <a class="link" 
href="https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html"; 
target="_top">Atomic
 Builtins</a>.)  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
 <code class="code">__gnu_parallel::_Settings::set</code>, respectively.
 Please note that the first call return a const object, so direct manipulation
 is forbidden.
-See <a class="link" 
href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html"; 
target="_top">
+See <a class="link" 
href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html"; 
target="_top">
   <code class="filename">&lt;parallel/settings.h&gt;</code></a>
 for complete details.
 </p><p>
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 <code class="literal">-fopenmp</code>. This will link
   in <code class="code">libgomp</code>, the
-  <a class="link" href="http://gcc.gnu.org/onlinedocs/libgomp/"; 
target="_top">GNU Offloading and
+  <a class="link" href="https://gcc.gnu.org/onlinedocs/libgomp/"; 
target="_top">GNU Offloading and
     Multi Processing Runtime Library</a>,
   whose presence is mandatory.
 </p><p>
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 <code class="literal">try</code> and <code 
class="literal">catch</code> blocks
     and thrown objects. (Language support
-    for <code class="literal">-fno-exceptions</code> is documented in the GNU
-    GCC <a class="link" 
href="http://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#Code-Gen-Options"; 
target="_top">manual</a>.)
+    for <code class="literal">-fno-exceptions</code> is documented in the GCC 
+    <a class="link" 
href="https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#Code-Gen-Options";
 target="_top">manual</a>.)
   </p><p>Before detailing the library support
     for <code class="literal">-fno-exceptions</code>, 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 <code>-fpack-struct</code> and
   <code>-fno-exceptions</code>, but include others: see the complete
-  list in the GCC manual under the heading <link 
xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="http://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#Code%20Gen%20Options";>Options
+  list in the GCC manual under the heading <link 
xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#Code%20Gen%20Options";>Options
   for Code Generation Conventions</link>.
 </para>
 
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
 <para>And for the rest, a simulated atomic lock via pthreads.
 </para>
 
-<para> Detailed information about compiler intrinsics for atomic operations 
can be found in the GCC <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="http://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html";> 
documentation</link>.
+<para>Detailed information about compiler intrinsics for atomic operations can 
be found in the GCC <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html";> 
documentation</link>.
 </para>
 
 <para> More details on the library fallbacks from the porting <link 
linkend="internals.thread_safety">section</link>.
@@ -290,7 +290,7 @@ the current host. In libstdc++ implementation files,
 </para>
 
 <para>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 <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html";>documentation</link>.
+use this layer. More detail as to the specific interface can be found in the 
source <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html";>documentation</link>.
 </para>
 
 <para>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);
     <quote>demangling.</quote>
   </para>
   <para>
-    If you have read the <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/namespaces.html";>source
+    If you have read the <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/namespaces.html";>source
     documentation for <code>namespace abi</code></link> 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.</para>
   flag <literal>-fopenmp</literal>. This will link
   in <code>libgomp</code>, the
   <link xmlns:xlink="http://www.w3.org/1999/xlink";
-    xlink:href="http://gcc.gnu.org/onlinedocs/libgomp/";>GNU Offloading and
+    xlink:href="https://gcc.gnu.org/onlinedocs/libgomp/";>GNU Offloading and
     Multi Processing Runtime Library</link>,
   whose presence is mandatory.
 </para>
@@ -739,7 +739,7 @@ i. e. it is a singleton. It can be read and written by 
calling
 <code>__gnu_parallel::_Settings::set</code>, respectively.
 Please note that the first call return a const object, so direct manipulation
 is forbidden.
-See <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html";>
+See <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/index.html";>
   <filename class="headerfile">&lt;parallel/settings.h&gt;</filename></link>
 for complete details.
 </para>
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:
        </para>
        <para>
 Selected when GCC supports a builtin atomic compare-and-swap operation
-on the target processor (see <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="http://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html";>Atomic
+on the target processor (see <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html";>Atomic
 Builtins</link>.)  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 <literal>try</literal> and <literal>catch</literal> blocks
     and thrown objects. (Language support
-    for <literal>-fno-exceptions</literal> is documented in the GNU
-    GCC <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="http://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#Code-Gen-Options";>manual</link>.)
+    for <literal>-fno-exceptions</literal> is documented in the GCC 
+    <link xmlns:xlink="http://www.w3.org/1999/xlink"; 
xlink:href="https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#Code-Gen-Options";>manual</link>.)
   </para>
 
   <para>Before detailing the library support

Reply via email to