public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 4da64180a139c25d9da85342fcbae5fef0de3b8c Date: Mon, 8 May 2023 12:11:06 +0000 (GMT) [thread overview] Message-ID: <20230508121106.952153858D32@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 4da64180a139c25d9da85342fcbae5fef0de3b8c (commit) from cb7e6cbe56b65b665e7abbedf66b271a87b39e1b (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 4da64180a139c25d9da85342fcbae5fef0de3b8c Author: Richard Biener <rguenther@suse.de> Date: Mon May 8 14:10:55 2023 +0200 GCC 12.3 release preparations diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 0854b83b..3816d06f 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -1141,9 +1141,6 @@ are not listed here).</p> <!-- .................................................................. --> <h2 id="12.3">GCC 12.3</h2> -<p>Note: GCC 12.3 has not been released yet, so this section is a -work-in-progress.</p> - <h3>Target Specific Changes</h3> <h3>x86-64</h3> @@ -1161,6 +1158,18 @@ known to be fixed in the 12.3 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here).</p> +<!-- .................................................................. --> +<h2 id="12.4">GCC 12.4</h2> + +<p>Note: GCC 12.4 has not been released yet, so this section is a +work-in-progress.</p> + +<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=12.4">list +of problem reports (PRs)</a> from GCC's bug tracking system that are +known to be fixed in the 12.4 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> diff --git a/htdocs/gcc-12/index.html b/htdocs/gcc-12/index.html index 1d886a1b..503bedd3 100644 --- a/htdocs/gcc-12/index.html +++ b/htdocs/gcc-12/index.html @@ -11,17 +11,23 @@ <h1>GCC 12 Release Series</h1> -<p>Aug 19, 2022</p> +<p>May 5, 2023</p> -<p>The GCC developers are pleased to announce the release of GCC 12.2.</p> +<p>The GCC developers are pleased to announce the release of GCC 12.3.</p> <p>This release is a bug-fix release, containing fixes for regressions in -GCC 12.1 relative to previous releases of GCC.</p> +GCC 12.2 relative to previous releases of GCC.</p> <h2>Release History</h2> <dl> +<dt>GCC 12.3</dt> +<dd>May 5, 2023 + (<a href="changes.html">changes</a>, + <a href="http://gcc.gnu.org/onlinedocs/12.3.0/">documentation</a>) +</dd> + <dt>GCC 12.2</dt> <dd>Aug 19, 2022 (<a href="changes.html">changes</a>, ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 15 ++++++++++++--- htdocs/gcc-12/index.html | 12 +++++++++--- 2 files changed, 21 insertions(+), 6 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-05-08 12:11 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=20230508121106.952153858D32@sourceware.org \ --to=rguenth@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).