From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 11.2.1 Status Report (2022-04-07)
Date: Thu, 7 Apr 2022 10:57:47 +0200 (CEST) [thread overview]
Message-ID: <1o17nnqr-o1p9-qn47-o93r-679oqspp46sq@fhfr.qr> (raw)
Status
======
The gcc-11 branch is in regression and documentation fixing mode.
It's time to prepare for the release of GCC 11.3 as we have accumulated
quite a number of fixes since GCC 11.2 was released. The plan is
to create a release candidate on Wednesday, April 13th, which is
in about one week and then follow with the release roughly a week
after that.
There are currently three P1 bugs which technically block the
release, we will not hold off releasing for PR102146 which is
extra testsuite failures on powerpc64le after backporting a change
from trunk. The other two bugs (PR102300, PR103871) are assigned,
so please try to fix them until next week or provide reasoning
why the regression from GCC 11.2 can be ignored (both are rejects-valid).
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 3 + 3
P2 448 + 186
P3 63 - 41
P4 223 + 17
P5 25 + 1
-------- --- -----------------------
Total P1-P3 514 + 148
Total 762 + 166
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2021-July/236903.html
reply other threads:[~2022-04-07 8:57 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=1o17nnqr-o1p9-qn47-o93r-679oqspp46sq@fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@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: link
Be 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).