Hi All, There's a bit of a disconnect between the feature flags that don't test the fpu and ones that do when the test itself also forces an architecture. The forcing of the architecture would change the defaults and without explicitly giving the correct fpu again the test would fail.
I don't see a good way to solve this problem, really the feature tests should ideally contain the extra options the test adds too, but for this specific case it can be solved by always testing the fpu explicitly. Committed under the GCC obvious Thanks, Tamar gcc/testsuite/ChangeLog: 2019-02-15 Tamar Christina <tamar.christ...@arm.com> * lib/target-supports.exp (check_effective_target_arm_neon_softfp_fp16_ok_nocache): Drop non-fpu checking alternative. --
diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index 1d237d4cd664924cc580cff67a563230b3fe9571..5d8ba4436ac1ad29da57802f2465d05712c8e8e7 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -3797,7 +3797,6 @@ proc check_effective_target_arm_neon_softfp_fp16_ok_nocache { } { if { [check_effective_target_arm32] && [check_effective_target_arm_neon_ok] } { foreach flags {"-mfpu=neon-fp16 -mfloat-abi=softfp" - "-mfloat-abi=softfp -mfp16-format=ieee" "-mfpu=neon-fp16 -mfloat-abi=softfp -mfp16-format=ieee"} { if { [check_no_compiler_messages_nocache arm_neon_softfp_fp16_ok object { #include "arm_neon.h"