From: sotrdg sotrdg <euloanty@live.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Why functions like memcpy, memmove in libgcc are not weak linkage?
Date: Fri, 24 Jun 2022 07:51:29 +0000 [thread overview]
Message-ID: <CH2PR02MB6522FC093CBDBC77990D8147B2B49@CH2PR02MB6522.namprd02.prod.outlook.com> (raw)
I think it might be very important to override the default implementations of memcpy and memmove since libgcc cannot really make a decision on how to generate the optimal code for specific platform.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
reply other threads:[~2022-06-24 7:51 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=CH2PR02MB6522FC093CBDBC77990D8147B2B49@CH2PR02MB6522.namprd02.prod.outlook.com \
--to=euloanty@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).