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. c4c0f59a6017f3cd17856719540784442debdde8 Date: Thu, 21 Apr 2022 07:40:42 +0000 (GMT) [thread overview] Message-ID: <20220421074042.16DF03858430@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 c4c0f59a6017f3cd17856719540784442debdde8 (commit) from 3e8c4b788a310070dab416f593458e9c46948cbd (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 c4c0f59a6017f3cd17856719540784442debdde8 Author: Richard Biener <rguenther@suse.de> Date: Thu Apr 21 09:40:28 2022 +0200 GCC 11.3 release preparations diff --git a/htdocs/develop.html b/htdocs/develop.html index 1ac48b09..d655dd34 100644 --- a/htdocs/develop.html +++ b/htdocs/develop.html @@ -676,9 +676,9 @@ stages of development, branch points, and releases:</p> | \ | v | GCC 11.2 release (2021-07-28) - GCC 12 Stage 3 (starts 2021-11-15) - | - GCC 12 Stage 4 (starts 2022-01-17) + GCC 12 Stage 3 (starts 2021-11-15) \ + | v + GCC 12 Stage 4 (starts 2022-01-17) GCC 11.3 release (2022-04-21) | v </pre> diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index c9eb2295..5f7e8481 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -1118,6 +1118,12 @@ are not listed here).</p> <h2 id="11.3">GCC 11.3</h2> +<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=11.3">list +of problem reports (PRs)</a> from GCC's bug tracking system that are +known to be fixed in the 11.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> + <h3>Target Specific Changes</h3> <h4>x86-64</h4> diff --git a/htdocs/gcc-11/index.html b/htdocs/gcc-11/index.html index 56c2ab5b..c2cc5d5f 100644 --- a/htdocs/gcc-11/index.html +++ b/htdocs/gcc-11/index.html @@ -11,17 +11,23 @@ <h1>GCC 11 Release Series</h1> -<p>July 28, 2021</p> +<p>April 21, 2022</p> -<p>The GCC developers are pleased to announce the release of GCC 11.2.</p> +<p>The GCC developers are pleased to announce the release of GCC 11.3.</p> <p>This release is a bug-fix release, containing fixes for regressions in -GCC 11.1 relative to previous releases of GCC.</p> +GCC 11.2 relative to previous releases of GCC.</p> <h2>Release History</h2> <dl> +<dt>GCC 11.3</dt> +<dd>April 21, 2022 + (<a href="changes.html">changes</a>, + <a href="http://gcc.gnu.org/onlinedocs/11.3.0/">documentation</a>) +</dd> + <dt>GCC 11.2</dt> <dd>July 28, 2021 (<a href="changes.html">changes</a>, diff --git a/htdocs/releases.html b/htdocs/releases.html index 1cadd0a9..2cad3a5e 100644 --- a/htdocs/releases.html +++ b/htdocs/releases.html @@ -33,6 +33,7 @@ releases and an alternative view of the release history.</p> <table class="padding5"> <tr><th>Release</th><th>Release date</th></tr> +<tr><td><a href="gcc-11/">GCC 11.3</a></td> <td>April 21, 2022</td></tr> <tr><td><a href="gcc-11/">GCC 11.2</a></td> <td>July 28, 2021</td></tr> <tr><td><a href="gcc-9/">GCC 9.4</a></td> <td>June 1, 2021</td></tr> <tr><td><a href="gcc-8/">GCC 8.5</a></td> <td>May 14, 2021</td></tr> ----------------------------------------------------------------------- Summary of changes: htdocs/develop.html | 6 +++--- htdocs/gcc-11/changes.html | 6 ++++++ htdocs/gcc-11/index.html | 12 +++++++++--- htdocs/releases.html | 1 + 4 files changed, 19 insertions(+), 6 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-04-21 7:40 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=20220421074042.16DF03858430@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).