This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Use the LTO linker plugin by default
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: Matthias Klose <doko at ubuntu dot com>
- Cc: Markus Trippelsdorf <markus at trippelsdorf dot de>, Richard Biener <rguenther at suse dot de>, gcc-patches at gcc dot gnu dot org, Jan Hubicka <hubicka at ucw dot cz>, Jakub Jelinek <jakub at redhat dot com>
- Date: Wed, 5 Mar 2014 08:14:08 +0100
- Subject: Re: [PATCH] Use the LTO linker plugin by default
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot LSU dot 2 dot 11 dot 1403041241510 dot 11121 at zhemvz dot fhfr dot qr> <20140304123055 dot GA11637 at x4> <5316C524 dot 7000908 at ubuntu dot com>
> Am 04.03.2014 13:30, schrieb Markus Trippelsdorf:
> > What is missing is a big fat warning in
> > http://gcc.gnu.org/gcc-4.9/changes.html that one should use the gcc
> > binutils wrappers (gcc-ar, etc.) when building projects with LTO.
>
> Is this enough? Or should the autoconf macros changed to look for these binaries
> if they exist? AC_PROG_AR, etc,
Help from autoconf side would be good (it needs to know that gcc is used for
compilation) I am not big fan of those wrappers, I think binutils should be
able to auto-load the plugin of system installed compilers
http://gcc.gnu.org/ml/gcc/2014-02/msg00128.html
But osmeone needs to implement it, too...
Also binutils can certainly be modified to output sane warning/error message
when they see slim GCC files (those are easily detectable) and have no plugin.
Honza
>
> Matthias