https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114568
Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clyon at gcc dot gnu.org, | |rearnsha at gcc dot gnu.org --- Comment #1 from Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> --- The test now fails with linker error: .../arm-eabi/bin/ld: error: /tmp/cc2Q27GE.o: conflicting architecture profiles A/M This is due to command line having -mthumb -march=armv7-m -mtune=cortex-m3 -mfloat-abi=softfp -mfpu=auto ... -mfpu=neon -mfloat-abi=softfp -march=armv7-a The first part comes from toolchain configuration settings, and the second part (-mfpu=neon -mfloat-abi=softfp -march=armv7-a) comes from check_effective_target_arm_neon_ok_nocache(). Surprisingly (to me), GCC accepts such mixed options, which makes check_effective_target_arm_neon_ok_nocache() succeed, since it's only doing a compilation test. The linker, though, fails. Richard E., it is expected that GCC accepts conflicting -march= options?