Pushed.
Gerald
libstdc++-v3:
* doc/xml/manual/using.xml: Switch gcc.gnu.org links to https.
* doc/html/manual/using_concurrency.html: Regenerate.
* doc/html/manual/using_dynamic_or_shared.html: Ditto.
* doc/html/manual/using_headers.html: Ditto.
* doc/html/manual/using_namespaces.html: Ditto.
---
libstdc++-v3/doc/html/manual/using_concurrency.html | 2 +-
.../doc/html/manual/using_dynamic_or_shared.html | 4 ++--
libstdc++-v3/doc/html/manual/using_headers.html | 2 +-
libstdc++-v3/doc/html/manual/using_namespaces.html | 2 +-
libstdc++-v3/doc/xml/manual/using.xml | 10 +++++-----
5 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/libstdc++-v3/doc/html/manual/using_concurrency.html
b/libstdc++-v3/doc/html/manual/using_concurrency.html
index e09fc5e15bc..d21f1588494 100644
--- a/libstdc++-v3/doc/html/manual/using_concurrency.html
+++ b/libstdc++-v3/doc/html/manual/using_concurrency.html
@@ -62,7 +62,7 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
and <code class="code">-march=native</code>, although specifics vary
depending on the host environment. See
<a class="link" href="using.html#manual.intro.using.flags"
title="Command Options">Command Options</a> and
- <a class="link"
href="http://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html";
target="_top">Machine
+ <a class="link"
href="https://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html";
target="_top">Machine
Dependent Options</a>.
</p></li><li class="listitem"><p>
An implementation of the
diff --git a/libstdc++-v3/doc/html/manual/using_dynamic_or_shared.html
b/libstdc++-v3/doc/html/manual/using_dynamic_or_shared.html
index f1e727800c2..a5a99ffef58 100644
--- a/libstdc++-v3/doc/html/manual/using_dynamic_or_shared.html
+++ b/libstdc++-v3/doc/html/manual/using_dynamic_or_shared.html
@@ -75,10 +75,10 @@
But how?
</p><p>
A quick read of the relevant part of the GCC
- manual, <a class="link"
href="http://gcc.gnu.org/onlinedocs/gcc/Invoking-G_002b_002b.html#Invoking-G_002b_002b";
target="_top">Compiling
+ manual, <a class="link"
href="https://gcc.gnu.org/onlinedocs/gcc/Invoking-G_002b_002b.html#Invoking-G_002b_002b";
target="_top">Compiling
C++ Programs</a>, specifies linking against a C++
library. More details from the
- GCC <a class="link" href="http://gcc.gnu.org/faq.html#rpath";
target="_top">FAQ</a>,
+ GCC <a class="link" href="https://gcc.gnu.org/faq.html#rpath";
target="_top">FAQ</a>,
which states <span class="emphasis"><em>GCC does not, by default,
specify a
location so that the dynamic linker can find dynamic libraries at
runtime.</em></span>
diff --git a/libstdc++-v3/doc/html/manual/using_headers.html
b/libstdc++-v3/doc/html/manual/using_headers.html
index a267e087a9d..5f669862654 100644
--- a/libstdc++-v3/doc/html/manual/using_headers.html
+++ b/libstdc++-v3/doc/html/manual/using_headers.html
@@ -186,5 +186,5 @@ g++ -Winvalid-pch -I. -include stdc++.h -H -g -O2 hello.cc
-o test.exe
! ./stdc++.h.gch
. /mnt/share/bld/H-x86-gcc.20071201/include/c++/4.3.0/iostream
. /mnt/share/bld/H-x86-gcc.20071201include/c++/4.3.0/string
-</pre><p>The exclamation point to the left of the <code
class="code">stdc++.h.gch</code> listing means that the generated PCH file was
used.</p><p></p><p> Detailed information about creating precompiled header
files can be found in the GCC <a class="link"
href="http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html";
target="_top">documentation</a>.
+</pre><p>The exclamation point to the left of the <code
class="code">stdc++.h.gch</code> listing means that the generated PCH file was
used.</p><p></p><p> Detailed information about creating precompiled header
files can be found in the GCC <a class="link"
href="https://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html";
target="_top">documentation</a>.
</p></div></div><div class="navfooter"><hr /><table width="100%"
summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p"
href="using.html">Prev</a>??</td><td width="20%" align="center"><a
accesskey="u" href="using.html">Up</a></td><td width="40%" align="right">??<a
accesskey="n" href="using_macros.html">Next</a></td></tr><tr><td width="40%"
align="left" valign="top">Chapter??3.??Using??</td><td width="20%"
align="center"><a accesskey="h" href="../index.html">Home</a></td><td
width="40%" align="right"
valign="top">??Macros</td></tr></table></div></body></html>
\ No newline at end of file
diff --git a/libstdc++-v3/doc/html/manual/using_namespaces.html
b/libstdc++-v3/doc/html/manual/using_namespaces.html
index b036d6fa6ac..1d0de6ca30d 100644
--- a/libstdc++-v3/doc/html/manual/using_namespaces.html
+++ b/libstdc++-v3/doc/html/manual/using_namespaces.html
@@ -13,7 +13,7 @@ and <code class="code">__gnu_pbds</code>.
</p></li></ul></div><p> The library uses a number of inline namespaces as
implementation
details that are not intended for users to refer to directly, these include
<code class="code">std::__detail</code>, <code
class="code">std::__cxx11</code> and <code class="code">std::_V2</code>.
-</p><p> A complete list of implementation namespaces (including namespace
contents) is available in the generated source <a class="link"
href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/namespaces.html";
target="_top">documentation</a>.
+</p><p>A complete list of implementation namespaces (including namespace
contents) is available in the generated source <a class="link"
href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/namespaces.html";
target="_top">documentation</a>.
</p></div><div class="section"><div class="titlepage"><div><div><h3
class="title"><a id="manual.intro.using.namespaces.std"></a>namespace
std</h3></div></div></div><p>
One standard requirement is that the library components are defined
in <code class="code">namespace std::</code>. Thus, in order to use
these types or
diff --git a/libstdc++-v3/doc/xml/manual/using.xml
b/libstdc++-v3/doc/xml/manual/using.xml
index 74321733e8f..6675359f3b3 100644
--- a/libstdc++-v3/doc/xml/manual/using.xml
+++ b/libstdc++-v3/doc/xml/manual/using.xml
@@ -1106,7 +1106,7 @@ g++ -Winvalid-pch -I. -include stdc++.h -H -g -O2
hello.cc -o test.exe
<para>The exclamation point to the left of the <code>stdc++.h.gch</code>
listing means that the generated PCH file was used.</para>
<para/>
-<para> Detailed information about creating precompiled header files can be
found in the GCC <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html";>documentation</link>.
+<para>Detailed information about creating precompiled header files can be
found in the GCC <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html";>documentation</link>.
</para>
</section>
@@ -1479,7 +1479,7 @@ details that are not intended for users to refer to
directly, these include
<code>std::__detail</code>, <code>std::__cxx11</code> and
<code>std::_V2</code>.
</para>
-<para> A complete list of implementation namespaces (including namespace
contents) is available in the generated source <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/namespaces.html";>documentation</link>.
+<para>A complete list of implementation namespaces (including namespace
contents) is available in the generated source <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/namespaces.html";>documentation</link>.
</para>
@@ -1722,10 +1722,10 @@ namespace gtk
</para>
<para>
A quick read of the relevant part of the GCC
- manual, <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/onlinedocs/gcc/Invoking-G_002b_002b.html#Invoking-G_002b_002b";>Compiling
+ manual, <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/onlinedocs/gcc/Invoking-G_002b_002b.html#Invoking-G_002b_002b";>Compiling
C++ Programs</link>, specifies linking against a C++
library. More details from the
- GCC <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/faq.html#rpath";>FAQ</link>,
+ GCC <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/faq.html#rpath";>FAQ</link>,
which states <emphasis>GCC does not, by default, specify a
location so that the dynamic linker can find dynamic libraries at
runtime.</emphasis>
@@ -1942,7 +1942,7 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
and <code>-march=native</code>, although specifics vary
depending on the host environment. See
<link linkend="manual.intro.using.flags">Command Options</link> and
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html";>Machine
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html";>Machine
Dependent Options</link>.
</para>
</listitem>
--
2.45.2
