From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: "'GNU C Library'" <libc-alpha@sourceware.org>,
"Cristian Rodríguez" <crrodriguez@opensuse.org>
Subject: [manual]: rawmemchr(3) and UB
Date: Fri, 30 Dec 2022 13:13:52 +0000 [thread overview]
Message-ID: <PAWPR08MB89824F0238DB1A045E0B9DF983F09@PAWPR08MB8982.eurprd08.prod.outlook.com> (raw)
Hi Alex,
> It seems I misunderstood your email. I've seen that glibc implements
> rawmemchr(3) in terms of strlen(3) and memchr(3). So it seems better to just
> not implement this function in my library, and optimize strlen(3) directly. The
> non-'\0' case seems useless, so probably not worth this function unless I see a
> use for it.
The idea is that compilers should treat it like mempcpy, bcopy etc and replace
all uses with standard strlen/memchr. GCC/LLVM don't do this yet for rawmemchr.
Since it is not in any standard and there is no benefit of having it, we should
obsolete this function along with all the other GNU extensions.
Cheers,
Wilco
next reply other threads:[~2022-12-30 13:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 13:13 Wilco Dijkstra [this message]
2022-12-30 14:16 ` Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 19:41 Wilco Dijkstra
2023-01-04 20:05 ` Alejandro Colomar
2023-01-04 20:19 ` G. Branden Robinson
2023-01-04 20:34 ` Alejandro Colomar
2023-01-05 12:21 ` G. Branden Robinson
2022-12-29 19:19 Alejandro Colomar
2022-12-29 19:27 ` Alejandro Colomar
2022-12-29 19:45 ` Cristian Rodríguez
2022-12-29 19:50 ` Alejandro Colomar
2022-12-30 10:31 ` Alejandro Colomar
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=PAWPR08MB89824F0238DB1A045E0B9DF983F09@PAWPR08MB8982.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=alx.manpages@gmail.com \
--cc=crrodriguez@opensuse.org \
--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).