* Why memcpy memmove memset are not weak symbol in libgcc?
@ 2022-02-08 16:20 unlvsur unlvsur
0 siblings, 0 replies; only message in thread
From: unlvsur unlvsur @ 2022-02-08 16:20 UTC (permalink / raw)
To: gcc-help
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>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-02-08 16:21 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-08 16:20 Why memcpy memmove memset are not weak symbol in libgcc? unlvsur unlvsur
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).