From: Florian Weimer <fweimer@redhat.com>
To: "Miller, Tim via Libc-help" <libc-help@sourceware.org>
Subject: Re: Build glibc for aarch64 with C-only versions of memcpy?
Date: Wed, 15 Dec 2021 21:40:51 +0100 [thread overview]
Message-ID: <87lf0lppnw.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <52DC392C-C51F-41DF-9120-574221C873A8@amazon.com> (Tim via Libc-help Miller's message of "Wed, 15 Dec 2021 20:31:55 +0000")
* Tim via Libc-help Miller:
> I am doing some software profiling on an aarch64 system, and I’m using
> the Linux perf tool. The problem I’m running into is that
> “__GI___memcpy_simd” keeps showing up as the function with the most
> CPU usage.
This sounds like a perf bug. Surely it can look at the LR register and
see where the call is coming from?
If it shows up so high in profiles, I suggest to attach a debugger and
see if you can get to it to stop in the memcpy call, and take things
from there.
Thanks,
Florian
next prev parent reply other threads:[~2021-12-15 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 20:31 Miller, Tim
2021-12-15 20:40 ` Florian Weimer [this message]
2021-12-15 21:13 ` Miller, Tim
2021-12-15 21:28 ` Miller, Tim
2021-12-15 21:33 ` Florian Weimer
2021-12-15 21:37 ` Miller, Tim
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=87lf0lppnw.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@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).