[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gcl-devel] Re: relocation overflow

From: Geoff Keating
Subject: Re: [Gcl-devel] Re: relocation overflow
Date: Thu, 21 Nov 2002 10:21:23 -0800

> Cc: Daniel Jacobowitz <address@hidden>, Alan Modra <address@hidden>,
>    address@hidden, address@hidden
> From: Camm Maguire <address@hidden>
> Date: 20 Nov 2002 21:45:23 -0500

> Greetings, and thanks for your reply!
> Geoff Keating <address@hidden> writes:
> > Daniel Jacobowitz <address@hidden> writes:
> > 
> > > On Wed, Nov 20, 2002 at 12:01:59PM -0500, Camm Maguire wrote:

> > > PowerPC GCC doesn't seem to have a long-calls option, so you're just
> > > out of luck if you can't fit things in 16MB.  Trampolines may be the
> > > way to go.
> > 
> > The way this is normally done, for programs that load arbitrary
> > modules, is that each module is a .so file, is built with -fpic, and
> > is loaded using the dlsym functions.  Then the limit is 32Mb per
> > module, and you can have as many modules as your address space can
> > fit; cross-module calls happen through a PLT which can perform long
> > jumps.
> OK, when I first read this, I thought that -fPIC would eliminate 24bit
> relocs.  I was mistaken, and have just verified that the reloc
> overflows are different, but still present, when adding -fPIC.  On
> rereading this, it appears as though the dlym code has trampolines to
> handle long calls on 24bit relocs.  Maybe I should look here.

Perhaps you are trying to load .o files, not .so files?  There should
be no *24 relocs in a .so file if all its contents are built with
-fpic or -fPIC.

- Geoffrey Keating <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]