This is the mail archive of the
mailing list for the GCC project.
Re: Enable -fuse-linker-plugin by default when possible
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Jan Hubicka <hubicka at ucw dot cz>
- Cc: gcc-patches at gcc dot gnu dot org, bonzini at gnu dot org, aoliva at redhat dot com, rguenther at suse dot de
- Date: Mon, 29 Nov 2010 07:10:42 -0800
- Subject: Re: Enable -fuse-linker-plugin by default when possible
- References: <20101128215916.GA8909@kam.mff.cuni.cz>
On Sun, Nov 28, 2010 at 1:59 PM, Jan Hubicka <email@example.com> wrote:
> this patch makes us to enable -fuse-linker-plugin by default when LTO is
> enabled and (plugin)ld support plugins. This was discussed at the GCC Summit
> BOF as change we want to make to avoid user confussion.
> (plugin enabled LTO behaves a lot saner by not requiring -fwhole-program for
> good optimizations and by not silently ignoring LTO objects in archives)
> The decision whether to build linker plugin is made by toplevel configure,
> while logic about plugin ld is in gcc configure. ?So I pass decision of
> toplevel configure as --with-plugin=yes into gcc configure and added logic
> autodetecting presence of --plugin-opt command line option or testing whether
> we build with in-tree gold or resonably recent GNU ld.
I'd like to point out that the current linker plugin implementation is a hack,
not a real solution:
Can we fix it properly before enabling it by default?