This is the mail archive of the gcc@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: [LTO merge][0/15] Description of the final 15 patches

From: Alan Modra <amodra at bigpond dot net dot au>
To: DJ Delorie <dj at redhat dot com>
Cc: Diego Novillo <dnovillo at google dot com>, gcc at gcc dot gnu dot org
Date: Tue, 29 Sep 2009 21:34:26 +0930
Subject: Re: [LTO merge][0/15] Description of the final 15 patches
References: <b798aad50909281758s1bfe5a16pabc674b8a8d42fcc@mail.gmail.com> <200909290246.n8T2kT3A012463@greed.delorie.com>

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/configure.in is relevant

# When building a shared libopcodes, link against the pic version of libiberty
# so that apps that use libopcodes won't need libiberty just to satisfy any
# libopcodes references.
# We can't do that if a pic libiberty is unavailable since including non-pic
# code would insert text relocations into libopcodes.

-- 
Alan Modra
Australia Development Lab, IBM

References:
- [LTO merge][0/15] Description of the final 15 patches
  - From: Diego Novillo
- Re: [LTO merge][0/15] Description of the final 15 patches
  - From: DJ Delorie

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