http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55780
Bug #: 55780
Summary: effective targets arm_arch_v*_multilib are not strict
enough
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
AssignedTo: [email protected]
ReportedBy: [email protected]
CC: [email protected]
Target: arm
The arm_arch_v*_multilib effective targets check that a minimal C program will
execute when compiled for a particular ARM processor, but the test used is an
empty program and the tests that use those checks have more complicated code.
All of the effective target checks pass using the gdb arm simulator or QEMU,
but some of the ftest-*.c tests then get illegal instructions or hang.
Checks for the ability to run programs on particular hardware should include
code that will only run on that hardware, as is done for effective target whose
keywords end in "_hw_available".
