> Jan Hubicka <hubi...@ucw.cz> writes: > > > * config/bootstrap-lto.mk: Use -ffat-lto-objects. > > * common.opt (ffat-lto-objects): Disable by default. > > * doc/invoke.texi (fat-lto-objects): Update documentation. > > * opts.c: Enable fat-lto-objects on lto plugin disable setups. > > This is breaking all tests with -flto -fno-use-linker-plugin. > > $ gcc/xgcc -B gcc/ ../gcc/testsuite/gcc.c-torture/execute/900409-1.c -w -flto > -fno-use-linker-plugin > /daten/cross/m68k-linux/m68k-linux/sys-root/usr/lib/crt1.o: In function > `_start': > /daten/m68k/build/glibc-2.18/csu/../ports/sysdeps/m68k/start.S:85: undefined > reference to `main' > collect2: error: ld returned 1 exit status
Hmm, I see. Seems I profilebootstrapped but later regtested only on plugin disabled gccfarm machine. I wonder if we shall require users to use -ffat-lto-objects in combination with -fno-use-linker-plugin (and thus document it and fix the testsuite) or find a way to make driver to pass the option transparently? Honza > > Andreas. > > -- > Andreas Schwab, SUSE Labs, sch...@suse.de > GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 > "And now for something completely different."
