public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dale Johannesen <dalej@apple.com>
To: dewar@gnat.com (Robert Dewar)
Cc: Dale Johannesen <dalej@apple.com>,
	tjw@omnigroup.com, Peter.Sasi@t-systems.co.hu, aj@suse.de,
	gcc@gcc.gnu.org
Subject: Re: [GCC 3.x] Performance testing for QA
Date: Tue, 03 Sep 2002 10:32:00 -0000	[thread overview]
Message-ID: <279B0E74-BF63-11D6-A404-003065C86F94@apple.com> (raw)
In-Reply-To: <20020902224940.E7865F2D75@nile.gnat.com>


On Monday, September 2, 2002, at 03:49 PM, Robert Dewar wrote:

> <<   I only reason I think its nice to have the compiler bootstrap as 
> part
> of the benchmark is to make sure that the compiler is fast.  Instead, I
> think it would be more interesting to see how fast the compiler could
> build all the other benchmarks -- not how fast it could build itself :)
>>>
>
> I disagree, gcc is a very interesting benchmark because of its locality
> patterns. It precisely is NOT a collection of tight loops, and unlike
> some of the other tests in SPEC, it is very hard to tune a compiler
> to do artifically well on the gcc benchmark.

Since the benchmark gcc is never fed any erroneous source while running
the benchmark, none of the error-handling stuff is ever executed.  With
profile-based optimization it's possible to move a lot of that stuff so
it never gets paged in; that's a significant win.  The same conditions
don't apply when running gcc normally, so this is fairly artificial.

  reply	other threads:[~2002-09-03 17:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 15:49 Robert Dewar
2002-09-03 10:32 ` Dale Johannesen [this message]
2002-09-03 11:17 ` Kevin Atkinson
  -- strict thread matches above, loose matches on Subject: below --
2002-09-03 14:25 Robert Dewar
2002-09-03 14:15 Robert Dewar
2002-09-03 13:56 Robert Dewar
2002-09-03 13:55 Robert Dewar
2002-09-03 14:05 ` Kevin Atkinson
2002-09-03 14:12 ` Dale Johannesen
2002-09-03 13:36 Robert Dewar
2002-09-03 13:41 ` Kevin Atkinson
2002-09-03 13:25 Robert Dewar
2002-09-03 13:31 ` Daniel Jacobowitz
2002-09-03 14:28   ` Jan Hubicka
2002-09-02 15:50 Robert Dewar
2002-09-02 14:47 Robert Dewar
2002-09-02 15:42 ` Timothy J. Wood
2002-09-02  6:12 Sasi Péter
2002-09-02 14:08 ` Andreas Jaeger

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=279B0E74-BF63-11D6-A404-003065C86F94@apple.com \
    --to=dalej@apple.com \
    --cc=Peter.Sasi@t-systems.co.hu \
    --cc=aj@suse.de \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=tjw@omnigroup.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).