https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91376
--- Comment #11 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> --- > (In reply to r...@cebitec.uni-bielefeld.de from comment #8) [...] >> I don't see how nm would come into play here. > > I thought you see the failure for all tests. Then one could use nm to identify > if LTO plugin is properly loaded. Ok, I see. >> $ gld.cmd >> ../../lto-wrapper -fresolution=cp_lto_pr90990_0.res -flinker-output=rel >> cp_lto_pr90990_0.o >> /vol/gcc/bin/gld-2.32.51: /var/tmp//ccKkavFd.lto.o: plugin needed to handle >> lto object >> [Leaving g++-dg-lto-pr90990-01.exe.lto_wrapper_args] >> [Leaving /var/tmp//ccKkavFd.lto.o] > > Can you please send me the *.o files so that I can investigate them? Sure, attached. >> There's no nm anywhere in sight. Besides, I find it very strange that >> out of hundreds if not thousends of LTO tests during this bootstrap, >> only a single one shows this error. If there were a fundamental >> problem, I'd expect a way larger number here. > > That's strange! The test-case is not special to me. So one would think. However, the fact that I'm not the only one seeing this particular failure suggests otherwise...
