From: Diego Novillo <dnovillo@google.com>
To: sje@cup.hp.com
Cc: andreasmeier80@gmx.de, dberlin@dberlin.org,
gcc-patches@gcc.gnu.org, iant@google.com
Subject: Re: Patch for PR tree-optimization/32941, bootstrap comparision failure
Date: Tue, 14 Aug 2007 14:15:00 -0000 [thread overview]
Message-ID: <46C1B807.8070404@google.com> (raw)
In-Reply-To: <200708131710.KAA05824@hpsje.cup.hp.com>
On 8/13/07 11:10 AM, Steve Ellcey wrote:
> What do people think about the approach?
Looks fine to me. 50 may be a bit too large, but I'm not really sure.
next prev parent reply other threads:[~2007-08-14 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 17:18 Steve Ellcey
2007-08-13 17:50 ` Ian Lance Taylor
2007-08-14 17:25 ` Steve Ellcey
2007-08-14 18:03 ` Steve Ellcey
2007-08-14 14:15 ` Diego Novillo [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-10 15:50 Steve Ellcey
2007-08-10 16:33 ` Ian Lance Taylor
2007-08-10 16:39 ` Diego Novillo
2007-08-10 21:45 ` Daniel Berlin
2007-08-10 21:58 ` Steve Ellcey
2007-08-10 22:05 ` Daniel Berlin
2007-08-10 22:18 ` Steve Ellcey
2007-08-10 22:00 ` Diego Novillo
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=46C1B807.8070404@google.com \
--to=dnovillo@google.com \
--cc=andreasmeier80@gmx.de \
--cc=dberlin@dberlin.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=sje@cup.hp.com \
/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).