diff options
author | Richard Earnshaw <rearnsha@arm.com> | 2024-09-12 14:24:55 +0100 |
---|---|---|
committer | Richard Earnshaw <rearnsha@arm.com> | 2024-09-12 16:07:46 +0100 |
commit | 9a94c8ffdc8b554a2d95e0101e96830efee58add (patch) | |
tree | d130c367c9f6797147e38d8da41821a8c63acf65 /gcc/testsuite/g++.dg/cpp23 | |
parent | 7d6c6a0d15c136a68d066c60da0f48265a2b1886 (diff) | |
download | gcc-9a94c8ffdc8b554a2d95e0101e96830efee58add.zip gcc-9a94c8ffdc8b554a2d95e0101e96830efee58add.tar.gz gcc-9a94c8ffdc8b554a2d95e0101e96830efee58add.tar.bz2 |
arm: testsuite: make use of -mcpu=unset/-march=unset
This patch makes use of the new ability to unset the CPU or
architecture flags on the command line to enable several more tests on
Arm. It doesn't cover every case and it does enable some tests that
now fail for different reasons when the tests are no-longer skipped;
these were failing anyway for other testsuite configurations, so it's
still an overall improvement.
There's some restructuring required to fully implement this change: we
could previously treat Xscale as an architecture, even though the
option set -mcpu=, we now need to handle this correctly so that we
unset the architecture rather than the CPU. To do this I've added a
new table for these variants and renamed the template functions to use
'cpu' rather than 'arch'. This entailed updating the two XScale
related tests accordingly.
gcc/testsuite/ChangeLog:
* lib/target-supports.exp: Move xscale to new generator table.
(check_effective_target_arm_arch_FUNC_ok): Add -mcpu=unset to the
list of flags.
(add_options_for_arm_arch_FUNC): Likewise.
(check_effective_target_arm_cpu_FUNC_ok): New function.
(add_options_for_arm_cpu_FUNC): Likewise.
(check_effective_target_arm_cpu_FUNC_link): Likewise.
(check_effective_target_arm_cpu_FUNC_multilib): Likewise.
* gcc.target/arm/g2.c: Update dg directives.
* gcc.target/arm/scd42-2.c: Likewise.
Diffstat (limited to 'gcc/testsuite/g++.dg/cpp23')
0 files changed, 0 insertions, 0 deletions