public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 4.5 Status Report (2009-09-19)
Date: Sun, 20 Sep 2009 01:00:00 -0000	[thread overview]
Message-ID: <20090920005957.GA21474@bromo.med.uc.edu> (raw)
In-Reply-To: <alpine.LNX.2.00.0909192244530.4520@zhemvz.fhfr.qr>

On Sat, Sep 19, 2009 at 10:57:38PM +0200, Richard Guenther wrote:
> 
> We've been accumulating quite a number of P1 bugs.  Entering Stage 3
> should allow to improve considerably here in a short time.
> 

Richard,
   Will the graphite code be under strict stage 3 rules or will it
have more leeway under stage 3? We still aren't seeing uniform code
improvements from graphite in benchmarks yet and it would be a shame
to postpone that until gcc 4.6.
             Jack

  parent reply	other threads:[~2009-09-20  1:00 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
2009-09-19 22:22   ` Richard Guenther
2009-09-20  1:21   ` Geert Bosch
2009-09-20  1:00 ` Jack Howarth [this message]
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=20090920005957.GA21474@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --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).