https://bugs.llvm.org/show_bug.cgi?id=41035
Szabolcs Nagy <szabolcs.n...@arm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |---
CC| |szabolcs.n...@arm.com
--- Comment #14 from Szabolcs Nagy <szabolcs.n...@arm.com> ---
(In reply to James Y Knight from comment #13)
> When a compile doesn't specify -ffreestanding, the compiler assumes that the
> functions provided by the environment's normal libc will be available to the
> link. (And in this case, glibc provides bcmp, so the compiler may assume
> bcmp's availability.)
bcmp is not specified by any standard and violates
the c and posix extern linkage namespace rules so
the compiler should not generate it, in particular
with static linking it may break applications that
use this symbol for something else (which is valid
use and works with glibc currently).
this is a bug that should be fixed.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
