From: Noah Goldstein <goldstein.w.n@gmail.com>
To: enh <enh@google.com>
Cc: libc-coord@lists.openwall.com, gcc@gcc.gnu.org,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [libc-coord] Add new ABI '__memcmpeq()' to libc
Date: Thu, 16 Sep 2021 16:59:51 -0500 [thread overview]
Message-ID: <CAFUsyf+1GLKH43jJ2jnzpkzKAGmcAmB=PAfEtikBhyw90EabVw@mail.gmail.com> (raw)
In-Reply-To: <CAJgzZoo499zc6513w=QDmSeHwC0mt-Ardr9d7ryy3QvJoDtLaw@mail.gmail.com>
On Thu, Sep 16, 2021, 4:50 PM enh via Libc-alpha <libc-alpha@sourceware.org>
wrote:
> plus testing for _equality_ can (as mentioned earlier) have slightly
> different properties from the three-way comparator behavior of
> bcmp()/memcmp().
>
How does bcmp() have a three-way comparator?
Or do you mean how it is currently implemented as an alias to memcmp()?
> On Thu, Sep 16, 2021 at 2:43 PM Joseph Myers <joseph@codesourcery.com>
> wrote:
>
> > On Thu, 16 Sep 2021, James Y Knight wrote:
> >
> > > Wouldn't it be far simpler to just un-deprecate bcmp?
> >
> > The aim is to have something to which calls can be generated in all
> > standards modes. bcmp has never been part of ISO C; there's nothing to
> > undeprecate there.
> >
> > --
> > Joseph S. Myers
> > joseph@codesourcery.com
> >
>
next prev parent reply other threads:[~2021-09-16 22:00 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 [this message]
2021-09-16 22:17 ` Chris Kennelly
2021-09-16 22:36 ` Joseph Myers
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='CAFUsyf+1GLKH43jJ2jnzpkzKAGmcAmB=PAfEtikBhyw90EabVw@mail.gmail.com' \
--to=goldstein.w.n@gmail.com \
--cc=enh@google.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).