diff options
| author | Richard Earnshaw <rearnsha@arm.com> | 2025-04-04 13:38:35 +0100 |
|---|---|---|
| committer | Richard Earnshaw <rearnsha@arm.com> | 2025-04-04 16:24:11 +0100 |
| commit | 6e79fa4a25769b2facf519aaf04b2a757dd3c887 (patch) | |
| tree | f1f661519ee728ba6128d8180f413cafd319c887 /libcpp/expr.cc | |
| parent | 03ac8886e5c1fa16da90276fd721a57fa9435f4f (diff) | |
| download | gcc-6e79fa4a25769b2facf519aaf04b2a757dd3c887.zip gcc-6e79fa4a25769b2facf519aaf04b2a757dd3c887.tar.gz gcc-6e79fa4a25769b2facf519aaf04b2a757dd3c887.tar.bz2 | |
arm: testsuite: restore dg-do-what-default in mve.exp
On Arm, running
make check-gcc RUNTESTFLAGS="dwarf2.exp=pr43190.c"
with a target list of "arm-qemu{,-mthumb}"
results in no errors. But running it with
make check-gcc RUNTESTFLAGS="{mve,dwarf2}.exp=pr43190.c"
results in unresolved tests while running the thumb variant. The problem
is that mve.exp is changing dg-do-what-default to "assemble", but failing
to restore the original value once its tests are complete. The result is
that all subsequent tests run with an incorrect underlying default value.
The fix is easy - save dg-do-what-default and restore it after the tests
are complete.
gcc/testsuite/ChangeLog:
* gcc.target/arm/mve/mve.exp: Save dg-do-what-default before
changing it. Restore it once done.
Diffstat (limited to 'libcpp/expr.cc')
0 files changed, 0 insertions, 0 deletions