All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <tr@thomasrast.ch>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: Profiling support?
Date: Sun, 16 Feb 2014 16:44:55 +0100	[thread overview]
Message-ID: <87wqgv2hag.fsf@thomasrast.ch> (raw)
In-Reply-To: <87d2itc2zv.fsf@fencepost.gnu.org> (David Kastrup's message of "Tue, 11 Feb 2014 12:17:40 +0100")

David Kastrup <dak@gnu.org> writes:

> Looking in the Makefile, I just find support for coverage reports using
> gcov.  Whatever is there with "profile" in it seems to be for
> profile-based compilation rather than using gprof.
[...]
> Is there a reason there are no prewired recipes or advice for using
> gprof on git?  Is there a way to get the work done, namely seeing the
> actual distribution of call times (rather than iterations) using gcov so
> that this is not necessary?

No reason I'm aware of, other than that nobody ever wrote it.

Note that I wouldn't exactly be surprised if the gcov targets had
bitrotted without anyone noticing.  I haven't heard of any heavy users.
I originally wrote them to do some basic test coverage analysis, but
that's about it.

-- 
Thomas Rast
tr@thomasrast.ch

  parent reply	other threads:[~2014-02-16 15:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 11:17 Profiling support? David Kastrup
2014-02-11 13:18 ` Duy Nguyen
2014-02-11 14:41   ` David Kastrup
2014-02-11 15:14     ` John Keeping
2014-02-11 15:19       ` David Kastrup
2014-02-11 20:53         ` David Kastrup
2014-02-16 15:44 ` Thomas Rast [this message]
2014-02-16 15:59   ` David Kastrup
2014-02-16 16:54     ` Thomas Rast
2014-02-16 17:05       ` David Kastrup

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=87wqgv2hag.fsf@thomasrast.ch \
    --to=tr@thomasrast.ch \
    --cc=dak@gnu.org \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.