From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: GCC 12.0.0 Status Report (2022-01-10), Stage 3 ends Jan 16th
Date: Mon, 10 Jan 2022 12:55:15 +0100 (CET) [thread overview]
Message-ID: <n1rrn1on-or9p-2668-53q1-qs75p64pr368@fhfr.qr> (raw)
Status
======
The GCC development branch is open for general bugfixing (Stage 3)
and will transition to regression and documentation fixing only
(Stage 4) on the end of Jan 16th.
Take the quality data below with a big grain of salt - most of the
new P3 classified bugs will become P1 or P2 (generally every
regression against GCC 11 is to be considered P1 if it concerns
primary or secondary platforms).
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 30 - 4
P2 307 + 1
P3 279 + 42
P4 220 + 13
P5 25
-------- --- -----------------------
Total P1-P3 616 + 39
Total 861 + 52
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2021-November/237741.html
reply other threads:[~2022-01-10 11:55 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=n1rrn1on-or9p-2668-53q1-qs75p64pr368@fhfr.qr \
--to=rguenther@suse.de \
--cc=fortran@gcc.gnu.org \
--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).