This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] LTO plugin for coff, part 1: break out ELF-specific code and enable COFF builds
- From: Jack Howarth <howarth at bromo dot med dot uc dot edu>
- To: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, Dave Korn <dave dot korn dot cygwin at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 2 Oct 2010 12:13:46 -0400
- Subject: Re: [PATCH] LTO plugin for coff, part 1: break out ELF-specific code and enable COFF builds
- References: <4CA7596D.3040801@gmail.com> <20101002160036.GI11272@gmx.de>
On Sat, Oct 02, 2010 at 06:00:36PM +0200, Ralf Wildenhues wrote:
> Hi Dave,
>
> * Dave Korn wrote on Sat, Oct 02, 2010 at 06:10:21PM CEST:
> > This patch separates out the ELF-specific code from the LTO plugin into a
> > separate source file, and adds autoconfigury to select that or a COFF-specific
> > source file at build time. It also adds a configure-time option,
> > --enable-lto-plugin, which forcibly overrides the default decision about
> > whether or not to build the LTO plugin.
>
> Please explain why the existing --enable-lto switch is not sufficient.
> The configure user API for LTO starts to look quite complex and
> unorganized, with --enable-lto, --enable-lto-plugin, and
> --enable-languages=lto. Put another way, the poor user shouldn't have
> to bother with the details, and will want LTO by default whenever
> possible.
>
> Thanks,
> Ralf
A good first step would be for the COFF targets to enable lto by default
for their existing lto infrastructure (as darwin has for Mach-O lto support).
This would greatly simplify lto for COFF end-users.
Jack