https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65316
--- Comment #6 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- (In reply to Tobias Burnus from comment #5) > Created attachment 34972 [details] > valgrind output (for the lto1 child call) > > (In reply to Jan Hubicka from comment #3) > > $ while true ; do ./xgcc -B ./ -r -nostdlib -O2 -fno-lto-odr-type-merging > > -flto one.o two.o ; done > > Still fails here with a fail rate of 6.2%. (I used: "for ((I=0; $I<1000; > I++))" to gather the data.) > > If I run "valgrind --trace-children=yes" (required as the failure is in lto1 > and not in (x)gcc), it shows the attached warnings. All these warnings are bogus (and are disabled in a --enable-checking=valgrind build).
