From: Daniel Jacobowitz <drow@mvista.com>
To: Robert Dewar <dewar@gnat.com>
Cc: dalej@apple.com, Peter.Sasi@t-systems.co.hu, aj@suse.de,
gcc@gcc.gnu.org, tjw@omnigroup.com
Subject: Re: [GCC 3.x] Performance testing for QA
Date: Tue, 03 Sep 2002 13:31:00 -0000 [thread overview]
Message-ID: <20020903203012.GA10309@nevyn.them.org> (raw)
In-Reply-To: <20020903202513.4ABABF2D4B@nile.gnat.com>
On Tue, Sep 03, 2002 at 04:25:13PM -0400, Robert Dewar wrote:
> <<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.
> >>
>
> Why would it be paged in if it is not executed?
If it's on the same page as something which is executed. This is one
of the major benefits of profile-driven optimization.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-09-03 20:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 13:25 Robert Dewar
2002-09-03 13:31 ` Daniel Jacobowitz [this message]
2002-09-03 14:28 ` Jan Hubicka
-- 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-02 15:50 Robert Dewar
2002-09-02 15:49 Robert Dewar
2002-09-03 10:32 ` Dale Johannesen
2002-09-03 11:17 ` Kevin Atkinson
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=20020903203012.GA10309@nevyn.them.org \
--to=drow@mvista.com \
--cc=Peter.Sasi@t-systems.co.hu \
--cc=aj@suse.de \
--cc=dalej@apple.com \
--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).