From: "Joseph S. Myers" <joseph@codesourcery.com>
To: gcc@gcc.gnu.org
Cc: rguenther@suse.de
Subject: GCC 4.7.0 Status Report (2011-10-11)
Date: Wed, 12 Oct 2011 02:55:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1110112040270.6918@digraph.polyomino.org.uk> (raw)
Status
======
Trunk remains in Stage 1 and based on the 4.6 release schedule this
should end around the end of October unless a small delay is useful to
help merge any development branches. Of the branches mentioned in the
last status report, it appears that only transactional-memory and
cxx-mem-model are aiming for at least partial merging for 4.7
(although not all branches had answers to the questions in that
report). The recent proposal for adding the D front end is also
clearly a 4.8 matter, not 4.7, unless the patches outside the
D-specific directories are ready very soon.
Quality Data
============
Priority # Change from Last Report
-------- --- -----------------------
P1 27 + 21
P2 98 + 3
P3 31 - 28
-------- --- -----------------------
Total 156 - 4
Previous Report
===============
http://gcc.gnu.org/ml/gcc/2011-09/msg00086.html
The next status report for 4.7.0 will be sent by Richard.
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2011-10-11 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 2:55 Joseph S. Myers [this message]
2011-10-12 7: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=Pine.LNX.4.64.1110112040270.6918@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).