This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] LTO plugin for coff, part 1: break out ELF-specific code and enable COFF builds


On Sat, Oct 02, 2010 at 08:36:16PM +0100, Dave Korn wrote:
> On 02/10/2010 18:14, Ralf Wildenhues wrote:
> > * Dave Korn wrote on Sat, Oct 02, 2010 at 07:05:02PM CEST:
> >> On 02/10/2010 17:13, Jack Howarth wrote:
> >>> On Sat, Oct 02, 2010 at 06:00:36PM +0200, Ralf Wildenhues wrote:
> 
>   Ralf, Jack: your arguments are persuasive.  How about if I re-do the
> configury so that a) LTO is enabled for windows by default, as it is for
> darwin, and b) the lto-plugin is enabled on (both) those platforms?

Dave,
   Part (a) should just require the change...

Index: configure.ac
===================================================================
--- configure.ac	(revision 164904)
+++ configure.ac	(working copy)
@@ -1788,7 +1788,7 @@
   AC_SUBST(libelfinc)
 fi],[if test x"$default_enable_lto" = x"yes" ; then
     case $target in
-      *-apple-darwin*) ;;
+      *-cygwin*|*-mingw* | *-apple-darwin*) ;;
       # On other non-ELF platforms, LTO must be explicitly enabled.
       *) enable_lto=no ;;
     esac

Regarding part (b), I am unclear if this lto-plugin will require the use
of binuils on darwin. If so, it will definitely be a niche change for darwin
as the vast majority of users will want to build with FSF gcc using the standard
darwin cctools from Xcode. IMHO, binutils is not likely to be well supported on
darwin for use beyond cross-platform builds of the darwin target. I definitely
would not want to see lto require binutils for standard usage.
            Jack

> 
>   (I'll add the Mach-O stub files to the plugin while I'm at it.)
> 
>     cheers,
>       DaveK


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]