Re: [PATCH] testsuite: outputs.exp: cleanup before running tests (was: Re: [PATCH] testsuite: outputs.exp: test for skip_atsave more thoroughly)

2022-06-21 Thread Richard Biener via Gcc-patches
On Tue, Jun 21, 2022 at 7:47 AM Alexandre Oliva via Gcc-patches wrote: > > On Jun 21, 2022, Alexandre Oliva wrote: > > > * gcc.misc-tests/outputs.exp (outest): Introduce quiet mode, > > Use the just-added dry-run infrastructure to clean up files that may > have been left over by interrupted

Re: [PATCH] testsuite: outputs.exp: test for skip_atsave more thoroughly

2022-06-21 Thread Richard Biener via Gcc-patches
On Tue, Jun 21, 2022 at 7:45 AM Alexandre Oliva via Gcc-patches wrote: > > > 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,

[PATCH] testsuite: outputs.exp: cleanup before running tests (was: Re: [PATCH] testsuite: outputs.exp: test for skip_atsave more thoroughly)

2022-06-20 Thread Alexandre Oliva via Gcc-patches
On Jun 21, 2022, Alexandre Oliva wrote: > * gcc.misc-tests/outputs.exp (outest): Introduce quiet mode, Use the just-added dry-run infrastructure to clean up files that may have been left over by interrupted runs of outputs.exp, which used to lead to spurious non-repeatable (self-fixing) fa

[PATCH] testsuite: outputs.exp: test for skip_atsave more thoroughly

2022-06-20 Thread Alexandre Oliva via Gcc-patches
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