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: Fix libjava x86-64 multilib

From: Jakub Jelinek <jakub at redhat dot com>
To: Alexandre Oliva <aoliva at redhat dot com>
Cc: Ulrich Weigand <Ulrich dot Weigand at de dot ibm dot com>, bo at sonofthor dot dk, gcc-patches at gcc dot gnu dot org
Date: Wed, 2 Oct 2002 18:08:20 -0400
Subject: Re: Fix libjava x86-64 multilib
References: <OF207226D9.1922DC87-ONC1256C46.005077A7@de.ibm.com> <orvg4kli8m.fsf@free.redhat.lsd.ic.unicamp.br>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Wed, Oct 02, 2002 at 05:04:57PM -0300, Alexandre Oliva wrote:
> On Oct  2, 2002, "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com> wrote:
> 
> > Same on s390x.  The linker will build a shared library from non-PIC
> > objects, but it will crash at runtime (unless you ensure that all
> > other referenced objects are within +-2GB).
> 
> Is +-2GB a reasonable assumption given the way the kernel chooses the
> location where shared libraries are loaded?  I suppose it might be,
> and then you might want to use pass_all for now

It is not. Consider say taking address of function which has PLT slot in
main binary. The shared library will have R_390_PC32DBL reloc for this,
yet the binary will be some ~ 0x4000000000 bytes away.

	Jakub

References:
- Re: Fix libjava x86-64 multilib
  - From: Ulrich Weigand
- Re: Fix libjava x86-64 multilib
  - From: Alexandre Oliva

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