From: "Martin Liška" <mliska@suse.cz>
To: Alejandro Colomar <alx.manpages@gmail.com>, gcc@gcc.gnu.org
Subject: Re: Missing optimization: mempcpy(3) vs memcpy(3)
Date: Mon, 12 Dec 2022 14:37:46 +0100 [thread overview]
Message-ID: <8f9d61cf-14a5-4099-e2b6-7c8cac47a28b@suse.cz> (raw)
In-Reply-To: <fdc766b8-7cfd-806b-3602-53e1ba9b277e@gmail.com>
On 12/9/22 18:11, Alejandro Colomar via Gcc wrote:
> I expect the compiler to be knowledgeable enough to call whatever is fastest, whatever it is, but be consistent in both cases. However, here are the results:
Hi.
Note the glibc implementation of mempcpy typically uses (calls) memcpy, thus
I don't see any problem with the code snippets you provided.
Cheers,
Martin
next prev parent reply other threads:[~2022-12-12 13:37 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 [this message]
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
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=8f9d61cf-14a5-4099-e2b6-7c8cac47a28b@suse.cz \
--to=mliska@suse.cz \
--cc=alx.manpages@gmail.com \
--cc=gcc@gcc.gnu.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).