This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: [Bug lto/46905] -flto -fno-lto does not disable lto
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: andi-gcc at firstfloor dot org <gcc-bugzilla at gcc dot gnu dot org>
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 9 Jan 2011 02:10:16 +0100
- Subject: Re: [Bug lto/46905] -flto -fno-lto does not disable lto
- References: <bug-46905-4@http.gcc.gnu.org/bugzilla/> <bug-46905-4-kno2sAVFIX@http.gcc.gnu.org/bugzilla/>
> slim lto will take some time (next stage1)
I was chatting about this with Diego yesterday and he seems to be fine with the
basic slim LTO patch getting in. So it seems to me that we might get the slim
LTO patch for 4.6.0 and flip the default for 4.7.0
> i also plan to drop most of the code because with forced plugin
> the elf code in collect2 should not be needed anymore.
I don't know. Current collect2 code is utterly broken by using wrong symbol
table at first place. With GNU LD getting plugin support the situation got
better, but we still have darwin target where we have no linker support at all.
Apple linker has plugin, so probably one can write plugin glue, but until that
happens, we probably want to keep collect2 path somehow useable.
What I am aware of WRT plugin and LTO is that currently plugin force LTO by
default. I.e.
gcc -flto t.c -c
gcc t.o
will result in WHOPR while producing a.out
I ended up enabling plugin by defualt since that is a must for plugin, but plugin
should be extended to work out whether -flto was passed on the command line (or
be better told by the driver as we don't want to duplicate parsing everywhere)
and when lto is not passed do not claim objects that are not slim.
Honza