From: Daniel Jacobowitz <drow@false.org>
To: binutils@sourceware.org
Subject: Re: curious gprof behaviour on trivial testcase
Date: Sat, 29 Apr 2006 18:49:00 -0000 [thread overview]
Message-ID: <20060429051541.GA13829@nevyn.them.org> (raw)
In-Reply-To: <1146276484.15759.326.camel@aretha.corp.specifix.com>
On Fri, Apr 28, 2006 at 07:08:04PM -0700, James E Wilson wrote:
> I tested this patch on x86_64-linux. There were no regressions. Not
> very meaningful since there is no gprof testsuite, but I tested it by
> hand on a trivial and non-trivial testcase. Without the patch I get an
> error on a trivial testcase. With the patch, I get a flat profile for a
> trivial testcase.
For what my opinion is worth, I think this is a great change. Every
time I try to use gprof on an application built without -pg I have to
go look up the argument to print the flat callgraph.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-29 5:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 16:56 James E Wilson
2006-04-29 18:49 ` Daniel Jacobowitz [this message]
2006-05-02 0:33 ` Ben Elliston
2006-05-02 10:55 ` Nick Clifton
2006-05-02 18:03 ` James E Wilson
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=20060429051541.GA13829@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.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).