aboutsummaryrefslogtreecommitdiff
path: root/libjava/gnu/java/security/ber/BEREncodingException.java
diff options
context:
space:
mode:
authorRichard Earnshaw <rearnsha@arm.com>2026-01-29 10:25:41 +0000
committerRichard Earnshaw <rearnsha@arm.com>2026-01-29 17:20:59 +0000
commit74907f407db641657ae71b67bb8625ad1efc8957 (patch)
treee4f542138dc40f1ff0980ffc6b38b7a4f2e38752 /libjava/gnu/java/security/ber/BEREncodingException.java
parent31875b910c70dd1e65d4da67562ac02b9b108c68 (diff)
downloadgcc-74907f407db641657ae71b67bb8625ad1efc8957.zip
gcc-74907f407db641657ae71b67bb8625ad1efc8957.tar.gz
gcc-74907f407db641657ae71b67bb8625ad1efc8957.tar.bz2
testsuite: arm: rework some target-supports checks to use -mfpu=auto
Several target-supports checks for Arm are still using the antiquated -mfpu=... setting rather than picking up FPU extensions via the architecture specification. This causes problems when tests are layered because they do not consistently override each other. Arguably, that is incorrect anyway: you can't test two sets of flag combinations independently and then expect to be able to apply both of them, but this change at least makes this behave in a reasonable way provided the second set of flags fully overrides the first. gcc/testsuite/ChangeLog: * lib/target-supports.exp: (check_effective_target_arm_v8_3a_complex_neon_ok_nocache): Split and fill in arm and aarch64 compile options. Remove the cpu_unset variable. (check_effective_target_arm_v8_2a_fp16_neon_ok_nocache): Likewise. (check_effective_target_arm_v8_3a_fp16_complex_neon_ok_nocache): Likewise. (check_effective_target_arm_neon_ok_nocache): Rework to use -mfpu=auto. (check_effective_target_arm_neon_fp16_ok_nocache): Likewise. Co-authored-by: Artemiy Volkov <artemiy.volkov@arm.com>
Diffstat (limited to 'libjava/gnu/java/security/ber/BEREncodingException.java')
0 files changed, 0 insertions, 0 deletions