linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Tibell <johan.tibell@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: Re: Symbols not decoded in 0.0.2.PERF
Date: Tue, 19 Apr 2011 17:58:06 +0200	[thread overview]
Message-ID: <BANLkTimUitmGOJKMk+YOgXOFNHiLCJCSGQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTike-f9qjdtjce+uiAPrjXgucn=5xQ@mail.gmail.com>

On Tue, Apr 19, 2011 at 1:22 PM, Johan Tibell <johan.tibell@gmail.com> wrote:
> * It could be the case that GHC is generating symbols that perf cannot
> interpret somehow. If we can confirm this is the case we can try to
> fix that.

I spent the day making sure this is not the case. All the Haskell
functions now have the correct (fingers crossed) .type and .size ELF
directives:

    74.18%            bench  ./bench               [.] 0x000000002ac524
     7.19%            bench  /lib/libc-2.11.1.so   [.] memcpy
     4.53%            bench  ./bench               [.] s1Ok_info
     4.28%            bench  ./bench               [.] s1Ol_info
     3.28%            bench  ./bench               [.] allocate
     0.74%            bench  ./bench               [.] Main_zdwa_info
     0.62%            bench  ./bench               [.] memcpy@plt
     0.45%            bench  ./bench               [.] clearNurseries
     0.36%            bench  ./bench               [.] evacuate
     0.27%            bench  ./bench               [.] stg_newArrayzh

Entries 3-6 and 8-10 are Haskell functions. The top entry is still unknown.

If it matters, the little program I'm running stresses array copying
and I would expect it to spend most of its time in memcpy, but these
numbers suggests that it isn't. Could it be some stripped C libraries
or some code generated by gcc specially for memcpy that's accounting
for the top entry?

Johan

  reply	other threads:[~2011-04-19 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 11:22 Symbols not decoded in 0.0.2.PERF Johan Tibell
2011-04-19 15:58 ` Johan Tibell [this message]
2011-04-20  8:55   ` Johan Tibell

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=BANLkTimUitmGOJKMk+YOgXOFNHiLCJCSGQ@mail.gmail.com \
    --to=johan.tibell@gmail.com \
    --cc=linux-perf-users@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 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 NNTP newsgroup(s).