Thanks. I agree that skipping DEBUG_INSNs can increase the search work for debug-heavy testcases, but it seems preferable to letting debug information change the ordinary-instruction search budget.
I tested the exact submitted patch, commit 63bd684c3c02021fe4c6b9a3247aaeecd19ef020, against the unmodified baseline at f311d59c4d45f5042029647c88966e2e48330adf. For the native testing, build, host, and target were all x86_64-pc-linux-gnu. I configured both trees with: configure --disable-multilib and ran: make -j8 bootstrap make -j8 -k check The bootstrap and complete testsuite run finished successfully. Comparing the generated .sum files against the baseline showed no new FAIL, XPASS, ERROR, or UNRESOLVED results. The seven pre-existing unexpected outcomes were identical between the baseline and patched trees. I also built a C cross compiler with build and host x86_64-pc-linux-gnu and target sparc-elf, then ran: make -j8 all-gcc make -C gcc check-gcc RUNTESTFLAGS=gcc.target/sparc/sparc.exp=pr127421.c The new gcc.target/sparc/pr127421.c regression test passes with the patch. I do not have GCC write access, so I would appreciate it if someone could commit the patch if the testing is sufficient.
