From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 5.3 Status Report (2015-11-20)
Date: Fri, 20 Nov 2015 12:53:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1511201353130.4884@t29.fhfr.qr> (raw)
Status
======
We plan to do a GCC 5.3 release candidate at the end of next week
followed by the actual release a week after that.
So now is the time to look at your regression bugs in bugzilla and
do some backporting for things already fixed on trunk.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 0
P2 121 + 30
P3 20 - 8
P4 87 + 2
P5 32 + 2
-------- --- -----------------------
Total P1-P3 141 + 22
Total 260 + 24
Previous Report
===============
https://gcc.gnu.org/ml/gcc/2015-07/msg00197.html
next reply other threads:[~2015-11-20 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 12:53 Richard Biener [this message]
2015-11-20 13:14 ` David Edelsohn
2015-11-22 13:49 ` Paolo Bonzini
2015-11-24 16:06 ` David Edelsohn
2015-11-25 16:58 ` Paolo Bonzini
2015-11-25 19:10 ` David Edelsohn
2015-11-26 9:33 ` Richard Biener
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.11.1511201353130.4884@t29.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).