From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 9.4.1 Status Report (2022-05-20)
Date: Fri, 20 May 2022 07:08:04 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2205200707320.4278@jbgna.fhfr.qr> (raw)
Status
======
The GCC 9 branch is now frozen for its final release, GCC 9.5.
The branch will be closed after that.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1
P2 369 - 58
P3 37 - 5
P4 186 - 2
P5 25
-------- --- -----------------------
Total P1-P3 406 - 58
Total 617 - 65
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2022-May/238655.html
reply other threads:[~2022-05-20 7:08 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.2205200707320.4278@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).