public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: Gerald Pfeifer <gerald@pfeifer.com>
Subject: [DOCS] sphinx: use new Sphinx links
Date: Wed, 9 Nov 2022 12:13:37 +0100	[thread overview]
Message-ID: <482ae3dd-15f7-1e81-92e6-51a148e3bbc4@suse.cz> (raw)

Pushed.

---
 htdocs/about.html                  |  2 +-
 htdocs/bugs/index.html             |  4 ++--
 htdocs/faq.html                    |  6 +++---
 htdocs/news.html                   |  4 ++--
 htdocs/projects/beginner.html      |  8 ++++----
 htdocs/projects/documentation.html |  2 +-
 htdocs/projects/gomp/index.html    | 12 ++++++------
 htdocs/releases.html               |  2 +-
 htdocs/simtest-howto.html          |  2 +-
 htdocs/style.mhtml                 |  8 ++++----
 htdocs/testing/index.html          |  6 +++---
 11 files changed, 28 insertions(+), 28 deletions(-)

diff --git a/htdocs/about.html b/htdocs/about.html
index 7278cae6..92e88ad0 100644
--- a/htdocs/about.html
+++ b/htdocs/about.html
@@ -17,7 +17,7 @@
 <p>The web effort was originally led by Jeff Law.  For the last two
 decades or so Gerald Pfeifer has been leading the effort, but there are
 many
-<a href="https://gcc.gnu.org/onlinedocs/gcc/Contributors.html">contributors
+<a href="https://gcc.gnu.org/onlinedocs/gcc/contributors-to-gcc.html">contributors
 </a>.</p>
 
 <p>The web pages are under <a href="#git">git control</a>.
diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index aaef8915..9b53512b 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -673,7 +673,7 @@ errors or malfunctioning programs.
 It should not be necessary to recompile if you have changed
 to a bug-fix release of the same version of the compiler; bug-fix
 releases are careful to avoid ABI changes. See also the
-<a href="https://gcc.gnu.org/onlinedocs/gcc/Compatibility.html">compatibility
+<a href="https://gcc.gnu.org/onlinedocs/gcc/binary-compatibility.html">compatibility
 section</a> of the GCC manual.</p>
 
 <h4>Standard conformance</h4>
@@ -689,7 +689,7 @@ However, some non-conforming constructs are allowed when the command-line
 option <code>-fpermissive</code> is used.</p>
 
 <p>The manual contains a section on
-<a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Misunderstandings.html">
+<a href="https://gcc.gnu.org/onlinedocs/gcc/known-causes-of-trouble-with-gcc/common-misunderstandings-with-gnu-c.html">
 Common Misunderstandings with GNU C++</a>.</p>
 
 </body>
diff --git a/htdocs/faq.html b/htdocs/faq.html
index b09e3920..0556b737 100644
--- a/htdocs/faq.html
+++ b/htdocs/faq.html
@@ -97,7 +97,7 @@ disadvantages.</p>
 <p>The host/target specific installation notes for GCC include information
 about known problems with installing or using GCC on particular platforms.
 These are included in the sources for a release in INSTALL/specific.html,
-and the <a href="https://gcc.gnu.org/install/specific.html">latest version</a>
+and the <a href="https://gcc.gnu.org/onlinedocs/install//host-target-specific-installation-notes-for-gcc.html">latest version</a>
 is always available at the GCC web site.
 Reports of <a href="buildstat.html">successful builds</a>
 for several versions of GCC are also available at the web site.</p>
@@ -210,7 +210,7 @@ may have to take one of the following actions to arrange that GCC uses
 the GNU versions of those programs.</p>
 
 <p>To ensure that GCC finds the GNU assembler (the GNU linker), which
-are required by <a href="https://gcc.gnu.org/install/specific.html">some
+are required by <a href="https://gcc.gnu.org/onlinedocs/install/host-target-specific-installation-notes-for-gcc.html">some
 configurations</a>,
 you should configure these with the same --prefix option as you used
 for GCC.  Then build &amp; install GNU as (GNU ld) and proceed with
@@ -427,7 +427,7 @@ those generated files are out of date and try to regenerate them.</p>
 transparently without requiring installation of any additional tools.</p>
 
 <p>If you modified some sources or when building from SVN you may also
-need <a href="https://gcc.gnu.org/install/prerequisites.html#TOC1">some
+need <a href="https://gcc.gnu.org/onlinedocs/install/install/prerequisites.html#tools-packages-necessary-for-modifying-gcc">some
 additional tools</a>.</p>
 
 
diff --git a/htdocs/news.html b/htdocs/news.html
index e1384852..2b35dabc 100644
--- a/htdocs/news.html
+++ b/htdocs/news.html
@@ -1020,7 +1020,7 @@ code now, and other ports will follow.
 <dd>
 Ben Elliston of Wasabi Systems, Inc. has converted the existing ARM
 processor pipeline description to the new <a
-href="https://gcc.gnu.org/onlinedocs/gccint/Processor-pipeline-description.html">DFA
+href="https://gcc.gnu.org/onlinedocs/3.4.0/gccint/Processor-pipeline-description.html">DFA
 pipeline description model</a>.
 It will be part of the GCC 3.4.0 release.
 </dd>
@@ -1075,7 +1075,7 @@ fix release only.
 <dd>
 Geoffrey Keating of Apple Computer, Inc., with support from Red Hat,
 Inc., has contributed a
-<a href="https://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html#Precompiled%20Headers">
+<a href="https://gcc.gnu.org/onlinedocs/3.4.0/gcc/Precompiled-Headers.html#Precompiled%20Headers">
 precompiled header</a> implementation that can dramatically speed up
 compilation of some projects.
 </dd>
diff --git a/htdocs/projects/beginner.html b/htdocs/projects/beginner.html
index 0cefb562..0825b2c0 100644
--- a/htdocs/projects/beginner.html
+++ b/htdocs/projects/beginner.html
@@ -31,10 +31,10 @@ suite.  You should also familiarize yourself with the
 
 <p>Many of these projects will require at least a reading knowledge of
 GCC's intermediate language,
-<a href="https://gcc.gnu.org/onlinedocs/gccint/RTL.html">RTL</a>.
+<a href="https://gcc.gnu.org/onlinedocs/gccint/rtl-representation.html">RTL</a>.
 It may help to understand the higher-level <code>tree</code> structure as
 well.  Unfortunately, for this we only have an <a
-href="https://gcc.gnu.org/onlinedocs/gccint/GENERIC.html">incomplete, C/C++ specific manual</a>.</p>
+href="https://gcc.gnu.org/onlinedocs/gccint/generic.html">incomplete, C/C++ specific manual</a>.</p>
 
 <p>Remember to <a href="../contributewhy.html">keep other developers
 informed</a> of any substantial projects you intend to work on.</p>
@@ -428,8 +428,8 @@ There is also work to be done in cleaning up the places where the MI
 code uses machine-specific macros.</p>
 
 <p>In addition to understanding RTL, you need to read the <a
-href="https://gcc.gnu.org/onlinedocs/gccint/Machine-Desc.html">machine description</a> and <a
-href="https://gcc.gnu.org/onlinedocs/gccint/Target-Macros.html">target macros</a> sections of the GCC
+href="https://gcc.gnu.org/onlinedocs/gccint/machine-descriptions.html">machine description</a> and <a
+href="https://gcc.gnu.org/onlinedocs/gccint/target-macros.html">target macros</a> sections of the GCC
 manual.</p>
 
 <ul>
diff --git a/htdocs/projects/documentation.html b/htdocs/projects/documentation.html
index 00d9217b..daed9036 100644
--- a/htdocs/projects/documentation.html
+++ b/htdocs/projects/documentation.html
@@ -58,7 +58,7 @@ a front end must or may provide.</p>
 
 <p>We've got quite a bit of this but it is scattered all over the
 place.  It belongs in the official manual.  There is a <a
-href="https://gcc.gnu.org/onlinedocs/gccint/GENERIC.html">C/C++ specific manual</a>,
+href="https://gcc.gnu.org/onlinedocs/gccint/generic.html">C/C++ specific manual</a>,
 which is incomplete, though.  The file
 <code>gcc/LANGUAGES</code> contains incomplete and outdated information
 about changes made in not so recent years to the <code>tree</code>
diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index 053e0b7d..713a4e16 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -36,21 +36,21 @@ OpenMP and OpenACC are supported with GCC's C, C++ and Fortran compilers.</p>
 <ul>
   <li>To enable <strong><a href="https://www.openmp.org">OpenMP</a></strong>,
   use <a
-  href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-fopenmp"
+  href="https://gcc.gnu.org/onlinedocs/gcc/gcc-command-options/options-controlling-c-dialect.html#cmdoption-fopenmp"
   ><code>-fopenmp</code></a>; <code>-fopenmp-simd</code> can be used
   to enable only the SIMD vectorization and loop-transformation constructs
   without creating multiple threads, offloading code or adding library
   dependency.</li>
   <li>To enable <strong><a href="https://www.openacc.org">OpenACC</a></strong>,
   use <a
-  href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-fopenacc"
+  href="https://gcc.gnu.org/onlinedocs/gcc/gcc-command-options/options-controlling-c-dialect.html#cmdoption-fopenacc"
   ><code>-fopenacc</code></a>.</li>
   <li>If either is enabled, offloading is automatically generated for all
   offload-device types for which the compiler has been configured. Use <a
-  href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-foffload"
+  href="https://gcc.gnu.org/onlinedocs/gcc/gcc-command-options/options-controlling-c-dialect.html#cmdoption-foffload"
   ><code>-foffload=</code></a> to disable or specify the offload-devices to be
   used. Use <a
-  href="https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-foffload-options"
+  href="https://gcc.gnu.org/onlinedocs/gcc/gcc-command-options/options-controlling-c-dialect.html#cmdoption-foffload-options"
   ><code>-foffload-options=</code></a> to pass device-specific compiler and
   linker flags.</li>
 </ul>
@@ -58,7 +58,7 @@ OpenMP and OpenACC are supported with GCC's C, C++ and Fortran compilers.</p>
 <p>Diagnostics</p>
 <ul>
   <li>The <a
-  href="https://gcc.gnu.org/onlinedocs/gcc/Developer-Options.html#index-fopt-info"
+  href="https://gcc.gnu.org/onlinedocs/gcc/gcc-command-options/gcc-developer-options.html#cmdoption-fopt-info"
   ><code>-fopt-info</code></a> flag provides details about compile-time performed
   optimizations.</li>
   <li>Environment variables can be used to influence run-time behavior and output
@@ -141,7 +141,7 @@ filing a <a href="../../bugs/">bug report</a>.</p>
 <h2 id="implementation-status">OpenMP Implementation Status</h2>
 
 <p>Implementation status in libgomp manual:
-<a href="https://gcc.gnu.org/onlinedocs/libgomp/OpenMP-Implementation-Status.html"
+<a href="https://gcc.gnu.org/onlinedocs/libgomp/openmp-implementation-status.html"
 >Mainline (GCC 13)</a>,
 <a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/libgomp/OpenMP-Implementation-Status.html"
 >GCC 12</a>.</p>
diff --git a/htdocs/releases.html b/htdocs/releases.html
index 02c675f5..22aa7928 100644
--- a/htdocs/releases.html
+++ b/htdocs/releases.html
@@ -19,7 +19,7 @@
 <p><em>Important: these are source releases, so will be of little
 use if you do not already have a C++ compiler installed.</em>
 As one option, there are
-<a href="https://gcc.gnu.org/install/binaries.html">pre-compiled
+<a href="https://gcc.gnu.org/onlinedocs/install/binaries.html">pre-compiled
 binaries.</a> for various platforms.</p>
 
 <p>You can also retrieve our sources <a href="git.html">using Git</a>.</p>
diff --git a/htdocs/simtest-howto.html b/htdocs/simtest-howto.html
index 2e54476b..cb9d109a 100644
--- a/htdocs/simtest-howto.html
+++ b/htdocs/simtest-howto.html
@@ -117,7 +117,7 @@ cd gcc &amp;&amp; find . -print | cpio -pdlmu ../combined &amp;&amp; cd ..
     <h2>Build it</h2>
 
     <p>Make sure the
-    <a href="http://gcc.gnu.org/install/prerequisites.html">building
+    <a href="http://gcc.gnu.org/onlinedocs/install/prerequisites.html">building
     prerequisites</a> for GCC are met, for example a host GCC no earlier
     than 3.4 or later, with C++ support enabled.</p>
 
diff --git a/htdocs/style.mhtml b/htdocs/style.mhtml
index 8afaa1e1..093f69a8 100644
--- a/htdocs/style.mhtml
+++ b/htdocs/style.mhtml
@@ -66,7 +66,7 @@
   <a href="<get-var BACKPATH>releases.html">Releases</a><br>
   <a href="<get-var BACKPATH>snapshots.html">Snapshots</a><br>
   <a href="<get-var BACKPATH>lists.html">Mailing lists</a><br>
-  <a href="https://gcc.gnu.org/onlinedocs/gcc/Contributors.html">Contributors</a><br>
+  <a href="https://gcc.gnu.org/onlinedocs/gcc/contributors-to-gcc.html">Contributors</a><br>
   <div class="center">
   <a href="https://twitter.com/gnutools">
     <img src="<get-var BACKPATH>twitter-bird-light-bgs.png"
@@ -84,8 +84,8 @@
   <tr><td><table class="navitem">
   <tr><td>Documentation</td></tr>
   <tr><td>
-  <a href="https://gcc.gnu.org/install/">Installation</a><br>
-  &middot;&nbsp;<a href="https://gcc.gnu.org/install/specific.html">Platforms</a><br>
+  <a href="https://gcc.gnu.org/onlinedocs/install/">Installation</a><br>
+  &middot;&nbsp;<a href="https://gcc.gnu.org/onlinedocs/install/host-target-specific-installation-notes-for-gcc.html">Platforms</a><br>
   <a href="<get-var BACKPATH>onlinedocs/">Manual</a><br>
   <a href="<get-var BACKPATH>faq.html">FAQ</a><br>
   <a href="https://gcc.gnu.org/wiki">Wiki</a><br>
@@ -97,7 +97,7 @@
   <tr><td>Download</td></tr>
   <tr><td>
   <a href="<get-var BACKPATH>mirrors.html">Mirrors</a><br>
-  <a href="https://gcc.gnu.org/install/binaries.html">Binaries</a>
+  <a href="https://gcc.gnu.org/onlinedocs/install/binaries.html">Binaries</a>
   </td></tr>
   </table></td></tr>
 
diff --git a/htdocs/testing/index.html b/htdocs/testing/index.html
index bd6219ab..e62254af 100644
--- a/htdocs/testing/index.html
+++ b/htdocs/testing/index.html
@@ -15,9 +15,9 @@
 for additional testing.</p>
 
 <p>For information about running the GCC testsuites, see
-<a href="https://gcc.gnu.org/install/test.html">Installing GCC: Testing</a>.
+<a href="https://gcc.gnu.org/onlinedocs/install/testing.html">Installing GCC: Testing</a>.
 For information about testsuite organization and adding new tests, see
-<a href="https://gcc.gnu.org/onlinedocs/gccint/Testsuites.html">
+<a href="https://gcc.gnu.org/onlinedocs/gccint/testsuites.html">
 Test Suites</a> in the GCC Internals manual and the README files in
 the testsuite directories.</p>
 
@@ -48,7 +48,7 @@ the testsuite directories.</p>
 <ul>
   <li>Perform regular builds and testing of current GCC sources that
       are not already being reported regularly; see
-      <a href="https://gcc.gnu.org/install/test.html">Installing GCC:
+      <a href="https://gcc.gnu.org/onlinedoc/install/testing.html">Installing GCC:
       Testing</a> for instructions on submitting test results.</li>
   <li>Build cross compilers and test with simulators as described in
       <a href="../simtest-howto.html">How to test GCC
-- 
2.38.0


             reply	other threads:[~2022-11-09 11:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 11:13 Martin Liška [this message]
2022-11-09 11:22 ` Martin Liška
2022-11-09 13:49   ` Martin Liška
2022-11-10  8:28     ` Gerald Pfeifer
2022-11-10  8:50       ` Martin Liška
2022-11-10  9:35         ` Gerald Pfeifer
2022-11-10  9:39           ` Martin Liška
2022-11-10 10:03             ` Gerald Pfeifer
2022-11-10 10:36               ` Martin Liška
2022-11-10 10:36               ` Tobias Burnus
2022-11-12  9:30                 ` Gerald Pfeifer
2022-11-12 19:12                   ` Gerald Pfeifer
2022-11-10 15:37           ` old install to a different folder Martin Liška
2022-11-10 19:24             ` Gerald Pfeifer
2022-11-11  8:40               ` Tobias Burnus
2022-11-11  8:50                 ` Martin Liška
2022-11-11  9:11                   ` Tobias Burnus
2022-11-11 10:18                     ` Richard Biener
2022-11-11 10:33                       ` Martin Liška
2022-11-11 10:37                       ` Tobias Burnus
2022-11-12  0:06                         ` Joseph Myers
2022-11-13 19:43                           ` Martin Liška
2022-11-14  1:21                             ` Gerald Pfeifer
2022-11-14  3:14                               ` Martin Liška
2022-11-09 22:13   ` [DOCS] sphinx: use new Sphinx links Gerald Pfeifer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=482ae3dd-15f7-1e81-92e6-51a148e3bbc4@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).