From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 13.0.1 Status Report (2023-02-22)
Date: Wed, 22 Feb 2023 10:14:57 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2302221013570.27913@jbgna.fhfr.qr> (raw)
Status
======
The GCC development branch which will become GCC 13 is in
regression and documentation fixing mode (Stage 4) until we
reach zero P1 regressions and branch for the release.
We are making slow progress towards this goal, new bugs are
coming in at a high pace.
Please help triaging UNCONFIRMED reported regressions and
at least provide some analysis for bugs attributed to you
or in the area of your expertise when they are classified
as target bugs.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 32 - 5
P2 492 - 5
P3 77 - 11
P4 255 - 1
P5 24
-------- --- -----------------------
Total P1-P3 601 - 21
Total 880 - 22
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2023-January/240523.html
reply other threads:[~2023-02-22 10:14 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.2302221013570.27913@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).