From: law@redhat.com
To: Carlo Wood <carlo@alinoe.com>
Cc: Michel LESPINASSE <walken@zoy.org>, Jan Hubicka <jh@suse.cz>,
Andreas Jaeger <aj@suse.de>, gcc list <gcc@gcc.gnu.org>
Subject: Re: GCC performance regression - up to 20% ?
Date: Mon, 22 Apr 2002 07:34:00 -0000 [thread overview]
Message-ID: <14166.1019485465@porcupine.cygnus.com> (raw)
In-Reply-To: Your message of Mon, 22 Apr 2002 15:58:01 +0200. <20020422155801.A21747@alinoe.com>
In message <20020422155801.A21747@alinoe.com>, Carlo Wood writes:
> >
> > Then I tried to figure out where the slowdown is, using gprof. And
> > this is where things get really interesting: gprof tells me that the
> > code compiled with 3.1 is faster, but 'time' tells me that the user
> > time spent executing that code is higher with 3.1 than with 2.95. I'm
> > not sure what to make of this, but I think this might give you some
> > clues, so I'll describe it in more detail. I'm not sure what the
> > overhead is, but it seems to be right in gprof's blind spot.
>
> gprof "measures" the time that a function takes by probing
> which function the program is executing about every 20 ms.
> >From that it builds up a statistical histogram.
>
> I wish there would be a more precise profiler that uses the
> hardware counters. Does anyone know of one? Hmm, I remember
> a Subject: line on the PAPI mailinglist that mentioned gprof,
> but I deleted it. I think it asked the same question: whether
> or not there existed a 'gprof' that used PAPI.
You might look at oprofile.
jeff
next prev parent reply other threads:[~2002-04-22 14:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 18:13 Michel LESPINASSE
2002-04-21 3:41 ` Andreas Jaeger
2002-04-21 5:46 ` Jan Hubicka
2002-04-21 23:46 ` Michel LESPINASSE
2002-04-22 0:17 ` Andreas Jaeger
2002-04-22 17:42 ` Michel LESPINASSE
2002-04-22 18:20 ` Andrew Pinski
2002-04-22 18:30 ` Carlo Wood
2002-04-22 19:25 ` Andrew Pinski
2002-04-24 15:24 ` Allan Sandfeld Jensen
2002-04-22 7:11 ` Carlo Wood
2002-04-22 7:11 ` Falk Hueffner
2002-04-22 7:34 ` law [this message]
2002-04-22 8:23 ` Johannes Stezenbach
2002-04-22 1:47 ` Gerald Pfeifer
2002-04-22 14:33 ` GCC performance regression - its memset ! Michel LESPINASSE
2002-04-22 14:58 ` Jason R Thorpe
2002-04-22 15:27 ` Michel LESPINASSE
2002-04-22 16:59 ` Segher Boessenkool
2002-04-22 17:10 ` Richard Henderson
2002-04-22 17:13 ` Michel LESPINASSE
2002-04-22 17:39 ` Richard Henderson
2002-04-22 17:49 ` Michel LESPINASSE
2002-04-23 5:03 ` Falk Hueffner
2002-04-23 6:53 ` Andreas Schwab
2002-04-23 2:39 ` Jan Hubicka
2002-04-23 13:36 ` Michel LESPINASSE
2002-04-24 0:30 ` Jan Hubicka
2002-04-24 0:50 ` Jakub Jelinek
2002-04-24 1:00 ` Jan Hubicka
2002-04-24 3:32 ` Jan Hubicka
[not found] <20020421005718.GA16378@zoy.org.suse.lists.egcs>
[not found] ` <20020421113238.GC16602@atrey.karlin.mff.cuni.cz.suse.lists.egcs>
2002-04-21 7:58 ` GCC performance regression - up to 20% ? Andi Kleen
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=14166.1019485465@porcupine.cygnus.com \
--to=law@redhat.com \
--cc=aj@suse.de \
--cc=carlo@alinoe.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=walken@zoy.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).