From: Geoff Keating <geoffk@geoffk.org>
To: rth@redhat.com
Cc: hjl@lucon.org, rmurray@cyberhqz.com, linux-mips@oss.sgi.com,
binutils@sourceware.cygnus.com, gcc@gcc.gnu.org
Subject: Re: linker problem: relocation truncated to fit
Date: Thu, 20 Sep 2001 15:52:30 -0700 [thread overview]
Message-ID: <200109202252.PAA02201@geoffk.org> (raw)
In-Reply-To: <20010917154754.E30386@redhat.com> (message from Richard Henderson on Mon, 17 Sep 2001 15:47:54 -0700)
> Date: Mon, 17 Sep 2001 15:47:54 -0700
> From: Richard Henderson <rth@redhat.com>
> Cc: Ryan Murray <rmurray@cyberhqz.com>, linux-mips@oss.sgi.com,
> binutils@sourceware.cygnus.com, gcc@gcc.gnu.org
> 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.
Actually, powerpc could use .sdata/.sbss for shared libraries, but it
never got implemented, and it would have the disadvantage that such
code can't be linked into non-shared objects.
It would be a significant speed/space win for certain objects, most
notably libm.
--
- Geoffrey Keating <geoffk@geoffk.org>
next prev parent reply other threads:[~2001-09-20 22:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 12:17 linker problem: relocation truncated to fit Petter Reinholdtsen
2001-09-16 16:16 ` H . J . Lu
2001-09-16 16:29 ` Wilbern Cobb
2001-09-16 16:29 ` Wilbern Cobb
2001-09-16 22:07 ` Petter Reinholdtsen
2001-09-16 22:38 ` Ryan Murray
2001-09-16 22:50 ` H . J . Lu
2001-09-17 1:55 ` Ralf Baechle
2001-09-17 22:40 ` Richard Henderson
2001-09-17 22:53 ` H . J . Lu
2001-09-17 22:56 ` Richard Henderson
2001-09-17 23:06 ` H . J . Lu
2001-09-17 23:01 ` Jakub Jelinek
2001-09-17 22:47 ` Richard Henderson
2001-09-17 22:56 ` Jakub Jelinek
2001-09-20 22:52 ` Geoff Keating [this message]
2001-09-26 10:08 ` Erik Corry
2001-09-16 22:50 ` Wilbern Cobb
2001-09-16 22:50 ` Wilbern Cobb
2001-09-17 1:50 ` Ralf Baechle
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=200109202252.PAA02201@geoffk.org \
--to=geoffk@geoffk.org \
--cc=binutils@sourceware.cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@redhat.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
--cc=rmurray@cyberhqz.com \
--cc=rth@redhat.com \
/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