From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
"H . J . Lu" <hjl.tools@gmail.com>,
Noah Goldstein <goldstein.w.n@gmail.com>
Subject: Re: [PATCH 00/12] Remove bcopy and bzero optimizations
Date: Mon, 14 Feb 2022 11:41:13 -0300 [thread overview]
Message-ID: <e518a57c-5f00-15fd-7c5a-5e2363152390@linaro.org> (raw)
In-Reply-To: <8735kl5xnv.fsf@oldenburg.str.redhat.com>
On 14/02/2022 11:29, Florian Weimer wrote:
> * Adhemerval Zanella via Libc-alpha:
>
>> On a recent Linux distro (Ubuntu 21.04), I see only 1 'bcmp' call
>> (which is already aliased to memcmp):
>
> Clang turns memcmp for equality (so basically __memcmpeq) into bcmp.
bcmp has the advantage we can alias to memcmp, so there is no need to
actually provide all the ifunc machinery.
next prev parent reply other threads:[~2022-02-14 14:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 19:58 Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 01/12] ia64: Remove bcopy Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 02/12] powerpc: Remove bcopy optimizations Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 03/12] i386: " Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 04/12] x86_64: " Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 05/12] alpha: Remove bzero optimization Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 06/12] ia64: " Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 07/12] " Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 08/12] powerpc: Remove powerpc32 bzero optimizations Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 09/12] powerpc: Remove powerpc64 " Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 10/12] s390: Remove " Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 11/12] i686: " Adhemerval Zanella
2022-02-10 19:58 ` [PATCH 12/12] x86_64: " Adhemerval Zanella
2022-02-14 14:29 ` [PATCH 00/12] Remove bcopy and " Florian Weimer
2022-02-14 14:41 ` Adhemerval Zanella [this message]
2022-02-21 16:39 ` Szabolcs Nagy
2022-02-22 15:40 ` Adhemerval Zanella
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=e518a57c-5f00-15fd-7c5a-5e2363152390@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Wilco.Dijkstra@arm.com \
--cc=fweimer@redhat.com \
--cc=goldstein.w.n@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).