From: Michel LESPINASSE <walken@zoy.org>
To: Jason R Thorpe <thorpej@wasabisystems.com>, gcc list <gcc@gcc.gnu.org>
Subject: Re: GCC performance regression - its memset !
Date: Mon, 22 Apr 2002 15:27:00 -0000 [thread overview]
Message-ID: <20020422221002.GA7330@zoy.org> (raw)
In-Reply-To: <20020422144125.S27275@dr-evil.shagadelic.org>
On Mon, Apr 22, 2002 at 02:41:25PM -0700, Jason R Thorpe wrote:
> gprof doesn't see it because gcc is doing the memset inline, presumably; it
> does this in certain cases where it knows the size at compile time.
I'm not surprised that there is no line for memset in the flat
profile. But, I'm surprised that the cumulative time in the flat
profile is not equal to the user time in the time command. 'normal'
inlines (i.e. the ones I could write by declaring an inline function)
are accounted normally by gprof (i.e. they do show up in the
cumulative time).
--
Michel "Walken" LESPINASSE
Is this the best that god can do ? Then I'm not impressed.
next prev parent reply other threads:[~2002-04-22 22:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 18:13 GCC performance regression - up to 20% ? 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
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 [this message]
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
2002-04-22 23:07 GCC performance regression - its memset! Roger Sayle
2002-04-22 23:30 ` Michel LESPINASSE
2002-04-23 0:45 ` Michel LESPINASSE
2002-04-23 2:53 ` Jan Hubicka
2002-04-23 3:28 ` Richard Henderson
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=20020422221002.GA7330@zoy.org \
--to=walken@zoy.org \
--cc=gcc@gcc.gnu.org \
--cc=thorpej@wasabisystems.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).