From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug string/25131] memcpy perfomance problem with ARM 32 A9be due to high cache-misses
Date: Mon, 25 Nov 2019 12:04:00 -0000 [thread overview]
Message-ID: <bug-25131-716-CH3NbSmojM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25131-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25131
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
--- Comment #6 from Florian Weimer <fweimer at redhat dot com> ---
The usual way we deal with this is to use some mechanism to probe for the
platform in question and use an IFUNC handler to switch to the optimized
version for this platform only.
I'm not sure if 32-bit Arm platform variants can be identified easily at the
CPU level or from the auxiliary vector. It may be necessary to do some kernel
work first.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-11-25 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25131-716@http.sourceware.org/bugzilla/>
2019-10-28 13:52 ` [Bug localedata/25131] " gunnarhj at ubuntu dot com
2019-10-28 13:57 ` [Bug malloc/25131] " gunnarhj at ubuntu dot com
2019-10-28 14:01 ` gunnarhj at ubuntu dot com
2019-10-28 15:52 ` [Bug string/25131] " jsm28 at gcc dot gnu.org
2019-11-22 6:33 ` helugang at huawei dot com
2019-11-22 9:08 ` gunnarhj at ubuntu dot com
2019-11-22 9:26 ` helugang at huawei dot com
2019-11-25 11:46 ` helugang at huawei dot com
2019-11-25 12:04 ` fweimer at redhat dot com [this message]
2019-11-25 12:08 ` fweimer at redhat 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-25131-716-CH3NbSmojM@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@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).