From: Jakub Jelinek <jakub@redhat.com>
To: gcc@gcc.gnu.org
Subject: GCC 8.3 Status Report (2019-02-09)
Date: Sat, 09 Feb 2019 09:11:00 -0000 [thread overview]
Message-ID: <20190209091151.GK2135@tucnak> (raw)
Status
======
Both GCC 8.3 P1s we had yesterday were fixed, so let's aim for the first
release candidate of 8.3 on February, 15th and, if all goes well, for
8.3 release on February, 22nd.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 0 - 1
P2 204 + 7
P3 25 - 3
P4 165
P5 24
-------- --- -----------------------
Total P1-P3 229 + 3
Total 418 + 3
Previous Report
===============
https://gcc.gnu.org/ml/gcc/2019-02/msg00027.html
next reply other threads:[~2019-02-09 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 9:11 Jakub Jelinek [this message]
2019-02-09 12:56 ` H.J. Lu
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=20190209091151.GK2135@tucnak \
--to=jakub@redhat.com \
--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).