https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98225
--- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #4 from Bernd Edlinger <edlinger at gcc dot gnu.org> --- > It is interesting that some tests are reported failing > on the x86_64-pc-linux-gnu platform that I also use. Right: it's not the platform per se but something about it or the tools used. > I really wonder what prevents these failures for me. The weird thing is that I've just run runtest --tool gcc outputs.exp in one of yesterday's build directories (build are currently running) and the only failures from outputs.exp are FAIL: outputs exe savetmp namedb: outputs.ld1_args FAIL: outputs exe savetmp named2: outputs.ld1_args FAIL: outputs exe savetmp named2: outputs.ld1_args FAIL: outputs exe savetmp named2: outputs.ld1_args Every other failure has vanished. > Could you say if there the outputs.exp test case > produces additional temp files in the /tmp folder when it fails? No: the only things left in /tmp from previous builds are from libgo make check.
