When compiling arm926ej-s programs, it appears that the resulting ELF headers
mark the compilations as VFP as well as software FP. When linking against a
generic lowest-common-denominator libc or libgcc, the linker complains the the
library modules are built as FPA (also software FP), and the VFP/FPA mismatch
produces the error:
libc.a(XXX.o) uses FPA instructions, whereas output.elf does not
That comes from elf32_arm_merge_private_bfd_data in elf32-arm.c.
The common workaround seems to be to add -mfpu=fpa to the compilation flags, and
-mfpu=softfpa to the assembler. But it seems to me that two software FP modules
should not be declared incompatible because of a mismatch in the kind of
floating fp instructions that they _don't_ have.
--
Summary: ARM linker gives spurious FPA-vs-VFP mismatches with
softfloat-only links (arm926ej-s)
Product: binutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: binutils
AssignedTo: unassigned at sources dot redhat dot com
ReportedBy: dporges at chipwrights dot com
CC: bug-binutils at gnu dot org
GCC host triplet: i686-pc-cygwin
GCC target triplet: arm-elf
http://sourceware.org/bugzilla/show_bug.cgi?id=5437
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils
