This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/61001] Builtin memcpy and memset cannot be overridden when -flto is used
- From: "hp at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 14 May 2014 21:13:49 +0000
- Subject: [Bug lto/61001] Builtin memcpy and memset cannot be overridden when -flto is used
- Auto-submitted: auto-generated
- References: <bug-61001-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61001
--- Comment #5 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
Well, it sucks as a failure mode. (User: "*Multiple* definitions? But I
provided *one*! Surely a linker bug/misfeature of some sorts!")
(Note: I'd be totally ok with e.g. compiling memcpy into a recursive function,
so the typical user may not agree!)
Anyway I'm less and less convinced that this behavior is desired (forgetting
about whatever functions happen to also be builtins when emitting the LTO
tentative symbols, then *re-introducing* them when emitting the real object
code).
See also PR55994.