From: Gerald Pfeifer Date: Thu, 11 Jul 2024 21:58:45 +0000 (+0200) Subject: libstdc++: Switch gcc.gnu.org links to https X-Git-Tag: basepoints/gcc-16~7576 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=26c9b095edf1ffa217f6cb2783b8ccfc5f4b1393;p=thirdparty%2Fgcc.git libstdc++: Switch gcc.gnu.org links to https 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. --- 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 -march=native, although specifics vary depending on the host environment. See Command Options and - Machine + Machine Dependent Options.

  • 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?

    A quick read of the relevant part of the GCC - manual, Compiling + manual, Compiling C++ Programs, specifies linking against a C++ library. More details from the - GCC FAQ, + GCC FAQ, which states GCC does not, by default, specify a location so that the dynamic linker can find dynamic libraries at runtime. 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 -

    The exclamation point to the left of the stdc++.h.gch listing means that the generated PCH file was used.

    Detailed information about creating precompiled header files can be found in the GCC documentation. +

    The exclamation point to the left of the stdc++.h.gch listing means that the generated PCH file was used.

    Detailed information about creating precompiled header files can be found in the GCC documentation.

    Prev Up Next
    Chapter 3. Using Home Macros
    \ 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 __gnu_pbds.

    • The library uses a number of inline namespaces as implementation details that are not intended for users to refer to directly, these include std::__detail, std::__cxx11 and std::_V2. -

    A complete list of implementation namespaces (including namespace contents) is available in the generated source documentation. +

    A complete list of implementation namespaces (including namespace contents) is available in the generated source documentation.

    namespace std

    One standard requirement is that the library components are defined in namespace std::. 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 The exclamation point to the left of the stdc++.h.gch listing means that the generated PCH file was used. - Detailed information about creating precompiled header files can be found in the GCC documentation. +Detailed information about creating precompiled header files can be found in the GCC documentation. @@ -1479,7 +1479,7 @@ details that are not intended for users to refer to directly, these include std::__detail, std::__cxx11 and std::_V2. - A complete list of implementation namespaces (including namespace contents) is available in the generated source documentation. +A complete list of implementation namespaces (including namespace contents) is available in the generated source documentation. @@ -1722,10 +1722,10 @@ namespace gtk A quick read of the relevant part of the GCC - manual, Compiling + manual, Compiling C++ Programs, specifies linking against a C++ library. More details from the - GCC FAQ, + GCC FAQ, which states GCC does not, by default, specify a location so that the dynamic linker can find dynamic libraries at runtime. @@ -1942,7 +1942,7 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33) and -march=native, although specifics vary depending on the host environment. See Command Options and - Machine + Machine Dependent Options.