From: Richard Guenther <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 4.7.0 Status Report (2011-10-27), Stage 1 will end Nov 7th
Date: Thu, 27 Oct 2011 12:58:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1110271404540.26779@zhemvz.fhfr.qr> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1559 bytes --]
Status
======
The GCC trunk is still in stage1. Stage1 will last until
Nov 7th (including, use your timezone to your advantage) after
which we will have been in stage1 for nearth 8 months.
In stage3 the trunk will be open for general bugfixing, no
new features will be accepted.
Now is time to bring down the number of regressions against
previous releases that we have accumulated. Especially if you
are a target or port maintainers consider reviewing bugreports
and make sure they are properly marked as regressions (if they are).
We do have quite a high number of release critical bugs (P1) right now,
some only because they do look important and did not yet get enough
attention for analysis. Which means you can also help with just
analyzing regressions even if you do not fix them.
Quality Data
============
Priority # Change from Last Report
-------- --- -----------------------
P1 51 + 24
P2 104 + 6
P3 15 - 16
-------- --- -----------------------
Total 170 + 14
We currently also have 118 P4 or P5 regression bugs open, those
include regressions for non-primary languages and targets that
are not included in the list of primary and secondary targets.
Previous Report
===============
http://gcc.gnu.org/ml/gcc/2011-10/msg00177.html
The next report will be sent by Jakub.
--
Richard Guenther <rguenther@suse.de>
SUSE / SUSE Labs
SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer
next reply other threads:[~2011-10-27 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 12:58 Richard Guenther [this message]
2011-10-27 14:47 Uros Bizjak
2011-11-15 15:28 ` Michael Zolotukhin
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.LNX.2.00.1110271404540.26779@zhemvz.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).