diff options
author | Alexandre Oliva <oliva@adacore.com> | 2022-06-21 23:10:58 -0300 |
---|---|---|
committer | Alexandre Oliva <oliva@gnu.org> | 2022-06-21 23:10:58 -0300 |
commit | 870f6866c96a38d30503d730ca3e9c3a5c320e32 (patch) | |
tree | 9b6a4f98ac1782987180840c616eff857a668cfe /gcc/tree-ssa-loop-ivopts.cc | |
parent | 614db2317e6519db9c77523498f5f14b860818d2 (diff) | |
download | gcc-870f6866c96a38d30503d730ca3e9c3a5c320e32.zip gcc-870f6866c96a38d30503d730ca3e9c3a5c320e32.tar.gz gcc-870f6866c96a38d30503d730ca3e9c3a5c320e32.tar.bz2 |
testsuite: outputs.exp: test for skip_atsave more thoroughly
The presence of -I or -L flags in link command lines changes the
driver's, and thus the linker's behavior, WRT naming files with
command-line options. With such flags, the driver creates .args.0 and
.args.1 files, whereas without them it's the linker (collect2, really)
that creates .ld1_args.
I've hit some fails on a target system that doesn't have -I or -L
flags in the board config file, but it does add some of them
implicitly with configured-in driver self specs. Alas, the test in
outputs.exp doesn't catch that, so we proceed to run rather than
skip_atsave tests.
I've reworked the outest procedure to allow dry runs and to return
would-have-been pass/fail results as lists, so we can now test whether
certain files are created and use that to configure the actual test
runs.
for gcc/testsuite/ChangeLog
* gcc.misc-tests/outputs.exp (outest): Introduce quiet mode,
create and return lists of passes and fails. Use it to catch
skip_atsave cases where -L flags are implicitly added by
driver self specs.
Diffstat (limited to 'gcc/tree-ssa-loop-ivopts.cc')
0 files changed, 0 insertions, 0 deletions