public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i at maskray dot me" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28153] [test] gmon/tst-gmon-gprof* may have a f3 line when built with ld.lld
Date: Fri, 30 Jul 2021 04:35:35 +0000 [thread overview]
Message-ID: <bug-28153-131-7Fx1JrSwU4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28153-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28153
--- Comment #2 from Fangrui Song <i at maskray dot me> ---
lld linked gmon/tst-gmon has f3.
% cd ~/Dev/glibc/out/lld
% ./testrun.sh gmon/tst-gmon
% gprof gmon/tst-gmon
...
Call graph (explanation follows)
granularity: each sample hit covers 4 byte(s) no time propagated
index % time self children called name
0.00 0.00 1000/2000 f2 [2]
0.00 0.00 1000/2000 f3 [3]
[1] 0.0 0.00 0.00 2000 f1 [1]
-----------------------------------------------
0.00 0.00 1000/1000 f3 [3]
[2] 0.0 0.00 0.00 1000 f2 [2]
0.00 0.00 1000/2000 f1 [1]
-----------------------------------------------
0.00 0.00 1/1 main [9]
[3] 0.0 0.00 0.00 1 f3 [3]
0.00 0.00 1000/1000 f2 [2]
0.00 0.00 1000/2000 f1 [1]
-----------------------------------------------
...
Index by function name
[1] f1 [2] f2 [3] f3
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-30 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 21:10 [Bug libc/28153] New: " i at maskray dot me
2021-07-29 16:50 ` [Bug libc/28153] " hjl.tools at gmail dot com
2021-07-30 4:35 ` i at maskray dot me [this message]
2021-07-30 22:48 ` hjl.tools at gmail dot com
2021-07-31 4:23 ` hjl.tools at gmail dot com
2021-08-24 14:18 ` hjl.tools at gmail dot com
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=bug-28153-131-7Fx1JrSwU4@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).