On Mon, Mar 28, 2011 at 12:14 PM, Rainer Orth <r...@cebitec.uni-bielefeld.de> wrote: > Richard Guenther <richard.guent...@gmail.com> writes: > >>> I think if the plugin linker is different from the normal linker we should >>> set HAVE_LTO_PLUGIN to 2. >> >> I think we should do the linker version checks which relate to linker-plugin >> use on the plugin-linker instead. So if I specify a separate but known > > I'll see if this is reasonably doable... > >> buggy linker I don't want it to be used by default. > > ... but how about a different route for 4.7? I've never really > understood the point of --with-plugin-ld. Given that we have known-good > linkers, why not simply remove that wart?
I sort-of agree, but for example for weird hosts like solaris we might want to give people the option to not replace their system linker unless they are using LTO. We could of course direct them to --with-ld instead, replacing the linker for a specific compiler only. What I'd like to remove for 4.7 is the -fuse-linker-plugin flag and non-linker-plugin operation (but that requires some more discussion). At least we should warn people if no linker with appropriate plugin-support was detected, as LTO support might be fragile then. Richard.
