From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Diego Novillo <dnovillo@google.com>
Cc: 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 02:03:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0909290131160.1054@digraph.polyomino.org.uk> (raw)
In-Reply-To: <b798aad50909281758s1bfe5a16pabc674b8a8d42fcc@mail.gmail.com>
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 is a
> shared object, and it uses libiberty functions, it needs
> to use a shared libiberty.
>
> Currently, we just force --enable-shared on libiberty,
> but I would only want to do that if gold and lto are
> enabled. We detect gold and lto support in the top
> configure script, but how do I send that down to
> libiberty's configure?
Shared libiberty seems like a bad idea as you then need to deal with
soname allocation and changing the soname whenever an ABI-incompatible
change is made. What you actually need is a PIC libiberty to link into
the plugin (and avoiding using any global data in libiberty that needs a
single copy in any program; hopefully it doesn't have any), not a shared
one.
(You also need to make sure this doesn't affect what is built for the
target, only for the host.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-09-29 2:03 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 [this message]
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
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=Pine.LNX.4.64.0909290131160.1054@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dnovillo@google.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
/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).