On Mon, 20 Nov 2023 at 08:42, Thomas Schwinge <tho...@schwinge.name> wrote:
>
> Hi!
>
> On 2023-10-15T23:42:39+0200, Gerald Pfeifer <ger...@pfeifer.com> wrote:
> > [ Release managers, heads-up for when you branch future releases! ]
>
> > For GCC 9 to GCC 13 the per-release series buildstat pages have not
> > been populated at all, so remove them and reference from the respective
> > main release pages.
>
> ACK; I had recently run into such an empty page, and wanted to suggest
> the same.
>
> We still need to update the docs some more. Do we just remove all
> references (and related text), and/or refer to the gcc-testresults
> mailing list?
>
> In wwwdocs:
>
> htdocs/branching.html:<li>Add <code>buildstat.html</code> and update the
> toplevel
> htdocs/branching.html:<code>buildstat.html</code> accordingly.</li>
>
> htdocs/faq.html:Reports of <a href="buildstat.html">successful builds</a>
> htdocs/faq.html-for several versions of GCC are also available at the web
> site.</p>
>
> htdocs/releasing.html-<li>For a new major release, ensure that the build
> status page is present
> htdocs/releasing.html:and add a link from the main
> <code>buildstat.html</code> page.</li>
>
> In GCC:
>
> gcc/doc/install.texi-Lists of successful builds for released versions of
> GCC are
> gcc/doc/install.texi:available at
> @uref{https://gcc.gnu.org/buildstat.html}.
> gcc/doc/install.texi-These lists are updated as new information becomes
> available.
>
> gcc/doc/install.texi-Some of these archived results are linked from the
> build status lists
> gcc/doc/install.texi:at @uref{https://gcc.gnu.org/buildstat.html},
> although not everyone who
> gcc/doc/install.texi-reports a successful build runs the testsuites and
> submits the results.
>
> gcc/doc/install.texi-If you are bootstrapping a released version of GCC
> then please
> gcc/doc/install.texi-quickly review the build status page for your
> release, available from
> gcc/doc/install.texi:@uref{https://gcc.gnu.org/buildstat.html}.
>
> libstdc++-v3/doc/xml/faq.xml- the rapid development and near-legendary
> libstdc++-v3/doc/xml/faq.xml: <link
> xmlns:xlink="http://www.w3.org/1999/xlink";
> xlink:href="https://gcc.gnu.org/buildstat.html";>portability</link>
> libstdc++-v3/doc/xml/faq.xml- that are the hallmarks of an open-source
> project are applied to libstdc++.
>
> libstdc++-v3/doc/xml/manual/test.xml- Archives of test results for
> various versions and platforms are
> libstdc++-v3/doc/xml/manual/test.xml: available on the GCC website
> in the <link xmlns:xlink="http://www.w3.org/1999/xlink";
> xlink:href="http://gcc.gnu.org/gcc-4.3/buildstat.html";>build
> libstdc++-v3/doc/xml/manual/test.xml- status</link> section of each
> individual release, and are also
> libstdc++-v3/doc/xml/manual/test.xml- archived on a daily basis on
> the <link xmlns:xlink="http://www.w3.org/1999/xlink";
> xlink:href="http://gcc.gnu.org/ml/gcc-testresults/current";>gcc-testresults</link>
Good point. I'll push the attached patch to the docs.
commit fd7a339512b60545700124b21700fb86a6527f76
Author: Jonathan Wakely <jwak...@redhat.com>
Date: Mon Nov 20 12:41:30 2023
libstdc++: Remove outdated references to buildstat.html
The buildstat.html pages have not existed since gcc-8 so remove
referencs to them in the libstdc++ manual.
libstdc++-v3/ChangeLog:
* doc/html/*: Regenerate.
* doc/xml/faq.xml: Remove reference to buildstat.html pages.
* doc/xml/manual/test.xml: Likewise
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index da41199584e..79edb02bec4 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -64,9 +64,8 @@
(<command>gcc</command>, <command>g++</command>, etc) is widely
considered to be one of the leading compilers in the world. Its
development is overseen by the
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/";>GCC team</link>. All of
- the rapid development and near-legendary
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/buildstat.html";>portability</link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/";>GCC team</link>.
+ All of the rapid development and near-legendary portability
that are the hallmarks of an open-source project are applied to libstdc++.
</para>
<para>
diff --git a/libstdc++-v3/doc/xml/manual/test.xml
b/libstdc++-v3/doc/xml/manual/test.xml
index 936f97417af..f2c709bc6bf 100644
--- a/libstdc++-v3/doc/xml/manual/test.xml
+++ b/libstdc++-v3/doc/xml/manual/test.xml
@@ -266,10 +266,8 @@ cat 27_io/objects/char/3_xin.in | a.out</programlisting>
<para>
Archives of test results for various versions and platforms are
- available on the GCC website in the <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/gcc-4.3/buildstat.html";>build
- status</link> section of each individual release, and are also
archived on a daily basis on the <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/ml/gcc-testresults/current";>gcc-testresults</link>
- mailing list. Please check either of these places for a similar
+ mailing list. Please check there for a similar
combination of source version, operating system, and host CPU.
</para>
</section>
