From: Jakub Jelinek <jakub@redhat.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: "Jonathan Wakely" <jwakely.gcc@gmail.com>,
"Martin Liška" <mliska@suse.cz>,
gcc@gcc.gnu.org, "GNU C Library" <libc-alpha@sourceware.org>
Subject: Re: Missing optimization: mempcpy(3) vs memcpy(3)
Date: Mon, 12 Dec 2022 17:09:59 +0100 [thread overview]
Message-ID: <Y5dSV6oL7Uipp1QG@tucnak> (raw)
In-Reply-To: <d4d02782-7fb3-19cf-e47b-af01b84b0462@gmail.com>
On Mon, Dec 12, 2022 at 04:56:27PM +0100, Alejandro Colomar wrote:
> "Names beginning with ‘str’, ‘mem’, or ‘wcs’ followed by a lowercase letter
> are reserved for additional string and array functions. See String and Array
> Utilities."
It is not that simple.
mem*, str* and wcs* are just potentially reserved identifiers, they are only
reserved if the implementation provided them. And what we discuss here
is how to reliably find out if it was an implementation that provided them,
because in case of gcc the implementation is GCC and the C library and
perhaps some other libraries too.
gcc can be used with lots of different C libraries, and many don't implement
mempcpy.
Jakub
next prev parent reply other threads:[~2022-12-12 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 17:11 Alejandro Colomar
2022-12-12 13:37 ` Martin Liška
2022-12-12 13:44 ` Alejandro Colomar
2022-12-12 13:56 ` Jakub Jelinek
2022-12-12 14:05 ` Alejandro Colomar
2022-12-12 14:48 ` Jonathan Wakely
2022-12-12 14:53 ` Jakub Jelinek
2022-12-12 15:56 ` Alejandro Colomar
2022-12-12 16:09 ` Jakub Jelinek [this message]
2022-12-12 17:15 ` Alejandro Colomar
2022-12-12 17:42 ` Jonathan Wakely
2022-12-12 14:34 Wilco Dijkstra
2022-12-12 14:57 ` Cristian Rodríguez
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=Y5dSV6oL7Uipp1QG@tucnak \
--to=jakub@redhat.com \
--cc=alx.manpages@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=mliska@suse.cz \
/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).