* Why functions like memcpy, memmove in libgcc are not weak linkage?
@ 2022-06-24 7:51 sotrdg sotrdg
0 siblings, 0 replies; only message in thread
From: sotrdg sotrdg @ 2022-06-24 7:51 UTC (permalink / 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-06-24 7:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-24 7:51 Why functions like memcpy, memmove in libgcc are not weak linkage? sotrdg sotrdg
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).