public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. cb67d8e215b08f58378afb5f9469788c1f58d4ac Date: Wed, 26 Apr 2023 07:03:28 +0000 (GMT) [thread overview] Message-ID: <20230426070328.B2D7B389EC68@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via cb67d8e215b08f58378afb5f9469788c1f58d4ac (commit) from 5756e2f89e367eb90c86093b9fda5819380af00a (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit cb67d8e215b08f58378afb5f9469788c1f58d4ac Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Apr 26 09:03:12 2023 +0200 Releasing 13.1. diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 87a43ea7..7b64b2e5 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -22,9 +22,6 @@ You may also want to check out our <a href="../onlinedocs/index.html#current">full GCC documentation</a>. </p> -<p>Note: GCC 13 has not been released yet, so this document is -a work-in-progress.</p> - <!-- .................................................................. --> <h2>Caveats</h2> <ul> @@ -791,7 +788,15 @@ a work-in-progress.</p> <!-- <h3 id="uninitialized">Eliminating uninitialized variables</h3> --> <!-- .................................................................. --> -<!-- <h2 id="13.1">GCC 13.1</h2> --> +<h2 id="13.1">GCC 13.1</h2> + +<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=13.0">list +of problem reports (PRs)</a> from GCC's bug tracking system that are +known to be fixed in the 13.1 release. This list might not be +complete (that is, it is possible that some PRs that have been fixed +are not listed here).</p> + +<!-- .................................................................. --> </body> </html> diff --git a/htdocs/gcc-13/index.html b/htdocs/gcc-13/index.html index f00b4be2..a610e15b 100644 --- a/htdocs/gcc-13/index.html +++ b/htdocs/gcc-13/index.html @@ -11,7 +11,24 @@ <h1>GCC 13 Release Series</h1> -<p>As of this time no releases of GCC 13 have yet been made.</p> +<p>April 26, 2023</p> + +<p>The GCC developers are pleased to announce the release of GCC 13.1.</p> + +<p>This release is a major release, containing new features (as well +as many other improvements) relative to GCC 12.x.</p> + +<h2>Release History</h2> + +<dl> + +<dt>GCC 13.1</dt> +<dd>April 26, 2023 + (<a href="changes.html">changes</a>, + <a href="http://gcc.gnu.org/onlinedocs/13.1.0/">documentation</a>) +</dd> + +</dl> <h2>References and Acknowledgements</h2> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 13 +++++++++---- htdocs/gcc-13/index.html | 19 ++++++++++++++++++- 2 files changed, 27 insertions(+), 5 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-04-26 7:03 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230426070328.B2D7B389EC68@sourceware.org \ --to=jakub@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /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: linkBe 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).