http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55780
--- Comment #2 from Janis Johnson <janis at gcc dot gnu.org> 2013-01-03 22:52:03 UTC --- Here's the configuration for the FSF mainline compiler I'm using: Target: arm-none-eabi Configured with: /scratch/janisjo/build6/fsf-arm-eabi/src/gcc-mainline/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-eabi --enable-threads --disable-libmudflap --disable-libssp --disable-libstdcxx-pch --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --disable-shared --enable-lto --with-newlib --disable-nls --prefix=/opt/codesourcery --with-headers=yes --with-sysroot=/opt/codesourcery/arm-none-eabi --with-build-sysroot=/scratch/janisjo/build6/fsf-arm-eabi/install/arm-none-eabi --disable-libgomp --disable-libitm Thread model: single gcc version 4.8.0 20130103 (experimental) (GCC) For this compiler, none of the links fail for the arm_arch_v*_multilib checks. Some of those checks fail at runtime, causing ftest-*.c tests to be UNSUPPORTED. In more cases, the simulator passes when running the arm_arch_v*_multilib check and then fails when running the test, causing it to FAIL instead of being UNSUPPORTED. It should be easy enough to add a check_link procedure, similar to check_compile or check_runtime, but from I've seen that would pass with all of these checks for my configuration. I suspect that a more robust link check would need target-specific code requiring calls to target-specific runtime libraries. A separate issue is that these checks are being used to determine whether or not to skip "dg-do run" tests, and that those tests can be rewritten to check the tested functionality at compile-time instead of run time; see <http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01339.html>.
