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 10:17:14PM +0100, Dave Korn wrote:
> On 02/10/2010 21:20, Jack Howarth wrote:
> 
> > Regarding part (b), I am unclear if this lto-plugin will require the use
> > of binuils on darwin.
> 
>   Well, yes, unless you can add it to cctools!
> 
> > 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.
> 
>   OK, but bear in mind that whether we build/install it is separate from
> whether we actually invoke it at runtime in the installed compiler, which is
> controlled by whether we have -fuse-linker-plugin or not.  I haven't yet
> figured out where exactly -fuse-linker-plugin comes from yet, but in general
> top-level configure can only decide what to build or not, while gcc/
> subconfigure is responsible for knowing the details of how to invoke target
> native tools at runtime.  So would you be OK with it getting built but unused,
> or would you like me to make it depend (in the darwin case only) on being
> configured --with-gnu-ld?

Dave,
   I would lean towards tethering it --with-gnu-ld. Iain should be able to test
this option since he appears to do regular builds against binutils for the darwin
targets.
                 Jack

> 
>     cheers,
>       DaveK


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