Paolo Bonzini writes:
> On 09/29/2009 06:52 PM, Ian Lance Taylor wrote:
>> Paolo Bonzini writes:
>>
So all Diego needs to do is pass --enable-shared down to libiberty
when --enable-lto/--enable-gold. The way to do that is something like
the appended.
>>>
>>> What about just alway
On 09/29/2009 06:52 PM, Ian Lance Taylor wrote:
Paolo Bonzini writes:
So all Diego needs to do is pass --enable-shared down to libiberty
when --enable-lto/--enable-gold. The way to do that is something like
the appended.
What about just always adding --enable-shared to the host libiberty?
Paolo Bonzini writes:
>> So all Diego needs to do is pass --enable-shared down to libiberty
>> when --enable-lto/--enable-gold. The way to do that is something like
>> the appended.
>
> What about just always adding --enable-shared to the host libiberty?
That will just cause everybody to always
So all Diego needs to do is pass --enable-shared down to libiberty
when --enable-lto/--enable-gold. The way to do that is something like
the appended.
What about just always adding --enable-shared to the host libiberty?
Paolo
On Tue, Sep 29, 2009 at 10:47, Ian Lance Taylor wrote:
> So all Diego needs to do is pass --enable-shared down to libiberty
> when --enable-lto/--enable-gold. The way to do that is something like
> the appended.
Thanks. Testing.
Diego.
"Joseph S. Myers" writes:
> On Mon, 28 Sep 2009, Diego Novillo wrote:
>
>> - libiberty
>> I need help with this one. When the linker plugin is
>> enabled (if GCC is configured to use gold), LTO can
>> detect LTO objects inside archives via the callbacks it
>> gets from the li
On Mon, Sep 28, 2009 at 22:00, Joseph S. Myers wrote:
> You say "tested on x86_64". More detail is needed. Have you tested both
Sorry, I completely spaced out and forgot to mention this. Various
folks are testing the branch. I sent a request for testing the branch
(http://gcc.gnu.org/ml/gcc/
On Mon, Sep 28, 2009 at 10:46:29PM -0400, DJ Delorie wrote:
>
> > gets from the linker. Since the linker plugin is a shared
> > object, and it uses libiberty functions, it needs to use a
> > shared libiberty.
>
> Why can't they just link a static libiberty?
This comment from opcodes
> gets from the linker. Since the linker plugin is a shared
> object, and it uses libiberty functions, it needs to use a
> shared libiberty.
Why can't they just link a static libiberty?
On Mon, 28 Sep 2009, Diego Novillo wrote:
> I will be sending the final 15 patches to bring all the
> functionality from the LTO branch. I tried to divide the patches
> along maintainer lines, but there are some overlaps
I'll go through the individual patches later, but a general comment:
You s
On Mon, 28 Sep 2009, Diego Novillo wrote:
> - libiberty
> I need help with this one. When the linker plugin is
> enabled (if GCC is configured to use gold), LTO can
> detect LTO objects inside archives via the callbacks it
> gets from the linker. Since the linker plugin i
I will be sending the final 15 patches to bring all the
functionality from the LTO branch. I tried to divide the patches
along maintainer lines, but there are some overlaps
- C FE
Adds processing of -flto and -fwhopr.
- C++ FE
Adds a langhook used by need_assembler_name_p to hand
12 matches
Mail list logo
