From: unlvsur unlvsur <unlvsur@live.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Why memcpy memmove memset are not weak symbol in libgcc?
Date: Tue, 8 Feb 2022 16:20:59 +0000 [thread overview]
Message-ID: <DM6PR05MB46977AA81A29DA69866656DED62D9@DM6PR05MB4697.namprd05.prod.outlook.com> (raw)
I think they should be weak defined to allow implementation to override the default implementation for a better implementation when it is impossible?
Since copy data fast is highly environmental specific
Get Outlook for Android<https://aka.ms/AAb9ysg>
reply other threads:[~2022-02-08 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=DM6PR05MB46977AA81A29DA69866656DED62D9@DM6PR05MB4697.namprd05.prod.outlook.com \
--to=unlvsur@live.com \
--cc=gcc-help@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).