http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55780
gretay at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gretay at gcc dot gnu.org
--- Comment #1 from gretay at gcc dot gnu.org 2013-01-02 12:17:07 UTC ---
The intention of arm_arch_v*_multilib is to check which multilibs available in
the toolchain rather than hardware capabilities. These effective target checks
fail at link time, but there is no check_link procedure in gcc/testsuite/lib so
check_runtime is used instead.
For example, using compiler with armv7a (cortex-a15) libraries only,
arm_arch_v6m_multilib effective target check fails and the test is UNSUPPORTED
in my setting on qemu:
$ cat arm_arch_v6m_multilib8582.c
int
main (void)
{
return 0;
}
$ /work/dec-builds/base/install/bin/arm-none-eabi-gcc
arm_arch_v6m_multilib8582.c -fno-diagnostics-show-caret -march=armv6-m
-mthumb -DSTACK_SIZE=16384 -lm -o arm_arch_v6m_multilib8582.exe
/work/dec-builds/base/install/lib/gcc/arm-none-eabi/4.8.0/../../../../arm-none-eabi/bin/ld:
error: /tmp/ccwSCtn0.o: Conflicting architecture profiles M/A
/work/dec-builds/base/install/lib/gcc/arm-none-eabi/4.8.0/../../../../arm-none-eabi/bin/ld:
failed to merge target specific data of file /tmp/ccwSCtn0.o
collect2: error: ld returned 1 exit status
UNSUPPORTED: gcc.target/arm/ftest-armv6m-thumb.c
Configured with: --target=arm-none-eabi --with-newlib --with-gnu-as
--with-gnu-ld --enable-languages=c,c++ --disable-shared --disable-nls
--disable-threads --disable-lto --disable-tls --enable-checking=yes
--disable-libssp --disable-libgomp --disable-libmudflap --with-cpu=cortex-a15
--with-fpu=neon-vfpv4 --with-float=softfp
Thread model: single
gcc version 4.8.0 20121213 (experimental) (GCC)
