From: Shawn Landden <shawn@git.icu>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-man@vger.kernel.org, Shawn Landden <shawn@git.icu>
Subject: [PATCH] bcmp: note that this function is no longer legacy due to LLVM 9
Date: Sat, 11 Jan 2020 18:55:44 +0400 [thread overview]
Message-ID: <20200111145544.5592-1-shawn@git.icu> (raw)
Signed-off-by: Shawn Landden <shawn@git.icu>
---
man3/bcmp.3 | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/man3/bcmp.3 b/man3/bcmp.3
index ba9838019..18d238720 100644
--- a/man3/bcmp.3
+++ b/man3/bcmp.3
@@ -70,15 +70,21 @@ T{
.BR bcmp ()
T} Thread safety MT-Safe
.TE
.SH CONFORMING TO
4.3BSD.
-This function is deprecated (marked as LEGACY in POSIX.1-2001): use
-.BR memcmp (3)
-in new programs.
+This function was deprecated (marked as LEGACY) by POSIX.1-2001).
POSIX.1-2008 removes the specification of
.BR bcmp ().
+LLVM 9, released in 2019, revived
+.BR bcmp ()
+and generates calls to it instead of
+.BR memcmp (3)
+as appropiate as an optimization (as
+.BR bcmp ()
+need not traverse memory in-order).
+.\" http://releases.llvm.org/9.0.0/docs/ReleaseNotes.html#noteworthy-optimizations
.SH SEE ALSO
.BR bstring (3),
.BR memcmp (3),
.BR strcasecmp (3),
.BR strcmp (3),
--
2.20.1
next reply other threads:[~2020-01-11 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 14:55 Shawn Landden [this message]
2020-01-17 11:57 ` [PATCH] bcmp: note that this function is no longer legacy due to LLVM 9 Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2020-01-11 14:50 Shawn Landden
2020-01-11 16:11 ` Dmitry V. Levin
2020-01-21 19:52 ` Michael Kerrisk (man-pages)
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=20200111145544.5592-1-shawn@git.icu \
--to=shawn@git.icu \
--cc=linux-man@vger.kernel.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 NNTP newsgroup(s).