From: unlvsur unlvsur <unlvsur@live.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Should GCC provide __builtin_memcpy_inline like clang does?
Date: Tue, 19 Jan 2021 11:33:56 +0000 [thread overview]
Message-ID: <DM6PR05MB46970FDD6B516073384F236ED6A39@DM6PR05MB4697.namprd05.prod.outlook.com> (raw)
I think __builtin_memmove_inline, __builtin_memset_inline can also get provided.
That allows better performance for small size copies and allowing memcpy to be usable without libc.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
next reply other threads:[~2021-01-19 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 11:33 unlvsur unlvsur [this message]
2021-01-19 18:51 ` Segher Boessenkool
2021-01-19 20:02 ` unlvsur unlvsur
2021-01-20 7:27 ` Richard Biener
2021-01-20 2:41 ` Gabriel Ravier
2021-01-20 2:52 ` H.J. Lu
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=DM6PR05MB46970FDD6B516073384F236ED6A39@DM6PR05MB4697.namprd05.prod.outlook.com \
--to=unlvsur@live.com \
--cc=gcc-help@gcc.gnu.org \
--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).