aboutsummaryrefslogtreecommitdiff
path: root/gcc/gimple-expr.c
diff options
context:
space:
mode:
authorTamar Christina <tamar.christina@arm.com>2019-02-15 17:17:17 +0000
committerTamar Christina <tnfchris@gcc.gnu.org>2019-02-15 17:17:17 +0000
commit75e2abe6f9a3b423e952b5741fcb2787834e19f4 (patch)
tree048e8967cae30643280e77b0ab158fb3e7ab4cf7 /gcc/gimple-expr.c
parent0a3d52ddee038a5b11eda5697f12d28019d83041 (diff)
downloadgcc-75e2abe6f9a3b423e952b5741fcb2787834e19f4.zip
gcc-75e2abe6f9a3b423e952b5741fcb2787834e19f4.tar.gz
gcc-75e2abe6f9a3b423e952b5741fcb2787834e19f4.tar.bz2
Arm: Remove alternative from neon_softfp_fp16 directive.
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 gcc/testsuite/ChangeLog: * lib/target-supports.exp (check_effective_target_arm_neon_softfp_fp16_ok_nocache): Drop non-fpu checking alternative. From-SVN: r268943
Diffstat (limited to 'gcc/gimple-expr.c')
0 files changed, 0 insertions, 0 deletions