From: Ian Lance Taylor <iant@google.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Diego Novillo <dnovillo@google.com>,
gcc@gcc.gnu.org, java@gcc.gnu.org,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: [LTO merge][0/15] Description of the final 15 patches
Date: Tue, 29 Sep 2009 18:54:00 -0000 [thread overview]
Message-ID: <mcrpr99bmzt.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <4AC23C1C.6090101@gnu.org> (Paolo Bonzini's message of "Tue\, 29 Sep 2009 18\:55\:56 +0200")
Paolo Bonzini <bonzini@gnu.org> writes:
> On 09/29/2009 06:52 PM, Ian Lance Taylor wrote:
>> Paolo Bonzini<bonzini@gnu.org> 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 compile libiberty twice. Why
>> do that if we don't have to?
>
> It's just a matter of time before we need to do that, anyway (say,
> when we have plugins that we distribute by default, for example for
> mudflap). Conditionalizing on GCC could be a middle ground, or maybe
> the worst possible choice? :-)
The shared libiberty is only required for the gold plugin. It's
possible to get benefits from LTO without the gold plugin. Which is a
good thing, since gold only works for a few targets.
Ian
next prev parent reply other threads:[~2009-09-29 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 0:58 Diego Novillo
2009-09-29 2:03 ` Joseph S. Myers
2009-09-29 14:48 ` Ian Lance Taylor
2009-09-29 14:56 ` Diego Novillo
2009-09-29 16:45 ` Paolo Bonzini
2009-09-29 16:53 ` Ian Lance Taylor
2009-09-29 16:56 ` Paolo Bonzini
2009-09-29 18:54 ` Ian Lance Taylor [this message]
2009-09-29 2:07 ` Joseph S. Myers
2009-09-29 13:06 ` Diego Novillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mcrpr99bmzt.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=bonzini@gnu.org \
--cc=dnovillo@google.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).