https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65126
--- Comment #4 from vries at gcc dot gnu.org --- (In reply to Maxim Kuvyrkov from comment #3) > Hi Tom, > > I can't reproduce this. I'm trying "make check-gcc RUNTESTFLAGS="vect.exp"" > on a native x86_64 bootstrap. > > What is required to trigger this? > Hi Maxim, vect.exp=vect-simd-clone-10.c should trigger this. Running vect-simd-clone-10.c produces the leftover vect-simd-clone-10a.c.126t.vect. But if vect-simd-clone-10a.c is run afterwards, then vect-simd-clone-10a.c.126t.vect is first overwritten, and then cleaned up. So whether the file is still there after the test run depends on whether 10a is run after 10 in the same testdirectory. Reproduced it with a fresh build from r220825: ... $ make -k -j5 check RUNTESTFLAGS=vect.exp=vect-simd-clone-10.c --target_board=unix ... $ ls lean/build/gcc/testsuite/gcc* lean/build/gcc/testsuite/gcc: gcc.log gcc.log.sep gcc.sum gcc.sum.sep site.exp lean/build/gcc/testsuite/gcc1: gcc.log.sep gcc.sum.sep site.exp vect-simd-clone-10a.c.126t.vect lean/build/gcc/testsuite/gcc2: gcc.log.sep gcc.sum.sep site.exp lean/build/gcc/testsuite/gcc3: gcc.log.sep gcc.sum.sep site.exp ...
