linux-mips
[Top] [All Lists]

Re: linker problem: relocation truncated to fit

To: "H . J . Lu" <hjl@lucon.org>
Subject: Re: linker problem: relocation truncated to fit
From: Richard Henderson <rth@redhat.com>
Date: Mon, 17 Sep 2001 15:47:54 -0700
Cc: Ryan Murray <rmurray@cyberhqz.com>, linux-mips@oss.sgi.com, binutils@sourceware.cygnus.com, gcc@gcc.gnu.org
In-reply-to: <20010916155003.B1446@lucon.org>; from hjl@lucon.org on Sun, Sep 16, 2001 at 03:50:03PM -0700
Mail-followup-to: Richard Henderson <rth@redhat.com>, "H . J . Lu" <hjl@lucon.org>, Ryan Murray <rmurray@cyberhqz.com>, linux-mips@oss.sgi.com, binutils@sourceware.cygnus.com, gcc@gcc.gnu.org
References: <20010916091654.C1812@lucon.org> <Pine.BSO.4.33.0109161323280.14503-100000@oddbox.cn> <20010917000719.B25531@false.linpro.no> <20010916153857.H22750@cyberhqz.com> <20010916155003.B1446@lucon.org>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5i
On Sun, Sep 16, 2001 at 03:50:03PM -0700, H . J . Lu wrote:
> I don't think mips is the only platform which has this problem. Do
> Alpha, PowerPC and Sparc have similar problems like that? What are
> the solutions for them?

Alpha has a complicated scheme by which every input object file may
be assigned to a different GOT, each of which is limited to 64k.  The
other reason this works is that variables assigned to .sdata/.sbss 
are _not_ treated differently wrt code generation.  Instead, this is
optimized via linker relaxation.

IA-64 will overflow its small data area at 22 bits.

PowerPC and Sparc do not use .sdata/.sbss.


r~

<Prev in Thread] Current Thread [Next in Thread>