public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 4.5 Status Report (2009-09-19)
Date: Sat, 19 Sep 2009 22:03:00 -0000	[thread overview]
Message-ID: <571f6b510909191502h78b4bd49nc9bcec0bb6338b12@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0909192244530.4520@zhemvz.fhfr.qr>

On Sat, Sep 19, 2009 at 10:57 PM, Richard Guenther <rguenther@suse.de> wrote:
> Since the last status report we have merged the VTA branch and pieces
> of the LTO branch.  The named address-spaces changes are still pending
> review but I expect it to be merged before the end of Stage 1.
> The rest of the LTO branch will be merged last, which practically
> means after Stage 1 is over.  Thus, starting Oct 1st the trunk will
> be frozen for the LTO merge and I'll announce Stage 3 once the merge
> is completed.

Is there a set of release criteria for all these major new features?
For example:

* testsuite for C/C++/Fortran should pass with LTO

* idem with WHOPR?

* GDB test suite should pass with -O1

* SPEC should pass with graphite

* ...


Also, IMHO a new requirement should be added for merging big new
features: Update changes.html.  As usual for the last, say, 4
releases, most of the interesting new features are not yet described
in the changes.html for the upcoming release (see
http://gcc.gnu.org/gcc-4.5/changes.html).

Ciao!
Steven

  reply	other threads:[~2009-09-19 22:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 20:57 Richard Guenther
2009-09-19 22:03 ` Steven Bosscher [this message]
2009-09-19 22:22   ` Richard Guenther
2009-09-20  1:21   ` Geert Bosch
2009-09-20  1:00 ` Jack Howarth
2009-09-20  1:35 ` Dave Korn
2009-09-20  8:54   ` Richard Guenther
2009-09-20 11:38     ` Dave Korn
2009-09-20 11:48       ` Richard Guenther
2009-09-20 11:53         ` Dave Korn
2009-09-24 14:44           ` Jason Merrill
2009-09-24 14:50             ` Richard Guenther
2009-09-21 18:23     ` Cary Coutant
2009-09-21 18:57       ` Jack Howarth
2009-09-21 21:05         ` Cary Coutant
2009-09-21 21:10           ` Cary Coutant
2009-09-29 18:10 ` Sriraman Tallam
2009-09-29 22:08 ` Dave Korn
2009-09-29 22:59   ` Gerald Pfeifer
2009-09-30 10:40     ` Richard Guenther
2009-09-30 15:00       ` Jack Howarth
2009-10-01  0:17 ` Neil Vachharajani

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=571f6b510909191502h78b4bd49nc9bcec0bb6338b12@mail.gmail.com \
    --to=stevenb.gcc@gmail.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).