From: Joseph Myers <joseph@codesourcery.com>
To: <libc-coord@lists.openwall.com>
Cc: GNU C Library <libc-alpha@sourceware.org>, <gcc@gcc.gnu.org>
Subject: Re: [libc-coord] Add new ABI '__memcmpeq()' to libc
Date: Thu, 16 Sep 2021 22:36:22 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2109162234400.2510762@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAEE+ybkH0B-HVUSdZVRXTaVYnt7=m54+UwkieRf5SuLDD1Xjxg@mail.gmail.com>
On Thu, 16 Sep 2021, Chris Kennelly wrote:
> The mem* functions are extremely sensitive to instruction cache effects, so
> having 3 unique implementations (__memcmpeq, bcmp, memcmp) that do similar,
I don't think anyone is suggesting 3 unique implementations. The
obsolescent name bcmp would be aliased to either __memcmpeq or memcmp
(depending on whether there are concerns about existing binaries depending
on bcmp acting like memcmp). (And __memcmpeq and memcmp would be aliases
on architectures without a separate optimized __memcmpeq.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-09-16 22:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 17:02 Noah Goldstein
2021-09-16 17:55 ` [libc-coord] " Chris Kennelly
2021-09-16 18:31 ` Noah Goldstein
2021-09-16 20:32 ` Chris Kennelly
2021-09-16 20:35 ` Joseph Myers
2021-09-16 20:55 ` enh
2021-09-17 7:43 ` Richard Biener
2021-09-17 8:08 ` Florian Weimer
2021-09-17 8:31 ` Richard Biener
2021-09-17 8:37 ` Florian Weimer
2021-09-17 9:30 ` Richard Biener
2021-09-17 17:40 ` Noah Goldstein
2021-09-17 9:12 ` Jakub Jelinek
2021-09-17 16:55 ` Martin Sebor
2021-09-17 14:19 ` Joseph Myers
2021-09-17 14:26 ` Florian Weimer
2021-09-21 19:53 ` Noah Goldstein
2021-09-22 17:46 ` Christoph Müllner
2021-09-22 18:15 ` Noah Goldstein
2021-09-16 21:27 ` James Y Knight
2021-09-16 21:42 ` Joseph Myers
2021-09-16 21:50 ` enh
2021-09-16 21:59 ` Noah Goldstein
2021-09-16 22:17 ` Chris Kennelly
2021-09-16 22:36 ` Joseph Myers [this message]
2021-09-16 23:24 ` Noah Goldstein
2021-09-18 1:36 ` James Y Knight
2021-10-26 22:47 ` Noah Goldstein
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=alpine.DEB.2.22.394.2109162234400.2510762@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-coord@lists.openwall.com \
/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).