From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org,
libstdc++@gcc.gnu.org,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: GCC 4.8.0 Status Report (2013-01-08), Stage 3 is over, regression fixes and docs only in effect immediately
Date: Tue, 08 Jan 2013 12:08:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1301081305010.6889@zhemvz.fhfr.qr> (raw)
Status
======
Stage3 has now officially ended after lasting a bit more than two months.
This means that GCC trunk is now in release branch mode, thus only
regression fixes and documentation changes are allowed now.
Upcoming GCC 4.8 has stabilized itself over the holidays and I am
aware of whole-distro rebuilds having taken place (x86_64, i586,
s390x and ppc). There are a high number of release critical bugs
around, several for less common (but primary or secondary) targets.
Target maintainers - please help confirming and analyzing bugs for
your targets.
GCC trunk will remain in release branch mode until the release managers
consider it fit for creating a first release candidate at which point
it will branch and development will open for the next stage1. History
tells us this will happen not earlier than two months from now.
Quality Data
============
Priority # Change from Last Report
-------- --- -----------------------
P1 25 + 2
P2 76 - 1
P3 18 - 73
-------- --- -----------------------
Total 119 - 72
Previous Report
===============
http://gcc.gnu.org/ml/gcc/2012-11/msg00095.html
The next report will be sent by Joseph.
next reply other threads:[~2013-01-08 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 12:08 Richard Biener [this message]
[not found] ` <Pine.LNX.4.64.1302142227440.26126@digraph.polyomino.org.uk>
2013-02-16 15:44 ` GCC 4.8.0 Status Report (2013-02-14) Gerald Pfeifer
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.1301081305010.6889@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=libstdc++@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).