https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61001
--- Comment #5 from Hans-Peter Nilsson ---
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 recur
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61001
Emmanuel Blot changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61001
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61001
--- Comment #2 from Marc Glisse ---
Please copy your testcase here.
-fno-builtin-memcmp is not a hack, it is necessary, even without -flto. Without
it, linking is not the only thing that may fail. gcc may look at your
implementation, recognize th
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61001
--- Comment #1 from Emmanuel Blot ---
Note: binutils version: 2.24