From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Subject: GCC 7.3 Status report (2017-12-18)
Date: Mon, 18 Dec 2017 10:35:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1712181134480.12252@zhemvz.fhfr.qr> (raw)
Status
======
GCC 7 is in regression and documentation fixes mode and it is time
to think about backports you want/need to do for GCC 7.3. The plan
is to do a release candidate for GCC 7.3 in the second week of January
following by a release a week after that.
As usual the branch is in good shape for what is considered release
critical but you might want to eye status on non-primary/secondary
targets and languages.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1
P2 161 + 22
P3 13 - 9
P4 153 - 3
P5 28
-------- --- -----------------------
Total P1-P3 174 + 13
Total 355 + 10
Previous Report
===============
https://gcc.gnu.org/ml/gcc/2017-08/msg00130.html
reply other threads:[~2017-12-18 10:35 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.1712181134480.12252@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).