From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 12.2.1 Status Report (2023-04-17)
Date: Mon, 17 Apr 2023 11:02:16 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2304171101100.4466@jbgna.fhfr.qr> (raw)
Status
======
The gcc-12 branch is open for regression and documentation fixes.
It's time to do the annual release from the branch, GCC 12.3, and
the planning is to do a release candidate at the start of the first
week of May following with the actual release in the second week.
Please look through bugzilla and see which of your regression fixes
for GCC 13 are also applicable for the GCC 12 branch and do the
necessary backporting. Note that releases from the older branches
will follow as well.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 1 + 1
P2 530 + 96
P3 56 - 8
P4 236 - 3
P5 24 - 1
-------- --- -----------------------
Total P1-P3 587 + 89
Total 847 + 85
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2022-August/239300.html
reply other threads:[~2023-04-17 11:02 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=nycvar.YFH.7.77.849.2304171101100.4466@jbgna.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).