From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Subject: GCC 9 Status Report (2019-03-29)
Date: Fri, 29 Mar 2019 12:26:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1903291325390.27537@zhemvz.fhfr.qr> (raw)
Status
======
We should be at the end of the stabilization phase (Stage 4) having
made some good progress in the long march towards zero P1 regressions.
Please have a look at those that you assigned yourself to.
There's still 12 P1 left at the moment though at some point bugs
not severe (wrong-code, rejects-valid) might be downgraded and
defered for fixing in a subsequent release. We would like to follow
the historical precedent of releasing at the end of April or the
beginning of May and not slip further.
As usual this is a good time to test your non-{primary,secondary}
target making sure it builds and works correctly.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 12 - 12
P2 158 - 27
P3 25 - 7
P4 138 - 31
P5 24
-------- --- -----------------------
Total P1-P3 195 - 46
Total 357 - 77
Previous Report
===============
https://gcc.gnu.org/ml/gcc/2019-02/msg00028.html
reply other threads:[~2019-03-29 12:26 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=alpine.LSU.2.20.1903291325390.27537@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--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).