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. f129583695e3d4fe384e1dfb553fd96f8a2a9e3e Date: Mon, 29 May 2023 08:45:22 +0000 (GMT) [thread overview] Message-ID: <20230529084523.081C63858434@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 f129583695e3d4fe384e1dfb553fd96f8a2a9e3e (commit) from 0006bbd9b6fab6089fd151526cbb9f4d594f07cd (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 f129583695e3d4fe384e1dfb553fd96f8a2a9e3e Author: Jakub Jelinek <jakub@redhat.com> Date: Mon May 29 10:44:15 2023 +0200 Releasing 11.4. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index cc0fdc19..44389172 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -1124,6 +1124,16 @@ 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> +<!-- .................................................................. --> + +<h2 id="11.4">GCC 11.4</h2> + +<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=11.4">list +of problem reports (PRs)</a> from GCC's bug tracking system that are +known to be fixed in the 11.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> + <h3>Target Specific Changes</h3> <h4>x86-64</h4> diff --git a/htdocs/gcc-11/index.html b/htdocs/gcc-11/index.html index 8e09a3c3..7cd96f7e 100644 --- a/htdocs/gcc-11/index.html +++ b/htdocs/gcc-11/index.html @@ -11,17 +11,23 @@ <h1>GCC 11 Release Series</h1> -<p>April 21, 2022</p> +<p>May 29, 2023</p> -<p>The GCC developers are pleased to announce the release of GCC 11.3.</p> +<p>The GCC developers are pleased to announce the release of GCC 11.4.</p> <p>This release is a bug-fix release, containing fixes for regressions in -GCC 11.2 relative to previous releases of GCC.</p> +GCC 11.3 relative to previous releases of GCC.</p> <h2>Release History</h2> <dl> +<dt>GCC 11.4</dt> +<dd>May 29, 2023 + (<a href="changes.html">changes</a>, + <a href="http://gcc.gnu.org/onlinedocs/11.4.0/">documentation</a>) +</dd> + <dt>GCC 11.3</dt> <dd>April 21, 2022 (<a href="changes.html">changes</a>, ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 10 ++++++++++ htdocs/gcc-11/index.html | 12 +++++++++--- 2 files changed, 19 insertions(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-05-29 8:45 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=20230529084523.081C63858434@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).