From: Joe Buck <jbuck@synopsys.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Scott Robert Ladd <coyote@coyotegulch.com>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Compiler Analysis: 3.3, 3.4, or tree-ssa?
Date: Thu, 16 Oct 2003 18:04:00 -0000 [thread overview]
Message-ID: <20031016102113.C2389@synopsys.com> (raw)
In-Reply-To: <u8r81ezaf6.fsf@gromit.moeb>; from aj@suse.de on Wed, Oct 15, 2003 at 07:18:53PM +0200
Scott Robert Ladd <coyote@coyotegulch.com> writes:
> > Now that I'm ready to publish Acovea (Analysis of Compiler Options Via
> > Evolutionary Algorithm), I'm wondering which version of gcc I should
> > analyze.
On Wed, Oct 15, 2003 at 07:18:53PM +0200, Andreas Jaeger wrote:
> 3.4 is soon in feature freeze, so it's too late for major changes.
Right, but if Scott should discover that, say, a different combination of
-f options in -O2 would be significantly better, it seems that this would
be a low-risk change that still could be accepted.
next prev parent reply other threads:[~2003-10-16 17:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 16:26 Scott Robert Ladd
2003-10-15 18:09 ` Andreas Jaeger
2003-10-15 19:34 ` Scott Robert Ladd
2003-10-16 15:58 ` Gerald Pfeifer
2003-10-16 16:20 ` Scott Robert Ladd
2003-10-18 14:12 ` Gerald Pfeifer
2003-10-16 18:04 ` Joe Buck [this message]
2003-10-17 11:48 ` Falk Hueffner
2003-10-17 12:52 ` Scott Robert Ladd
2003-10-17 18:48 Matthew Fago
2003-10-18 11:17 ` Scott Robert Ladd
2003-10-18 12:10 ` Matt Fago
2003-10-18 16:16 ` Scott Robert Ladd
2003-10-21 0:04 ` tm_gccmail
2003-10-21 6:47 ` Scott Robert Ladd
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=20031016102113.C2389@synopsys.com \
--to=jbuck@synopsys.com \
--cc=aj@suse.de \
--cc=coyote@coyotegulch.com \
--cc=gcc@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).