From: Richard Henderson <rth@redhat.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Ryan Murray <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: Mon, 17 Sep 2001 15:47:54 -0700 [thread overview]
Message-ID: <20010917154754.E30386@redhat.com> (raw)
In-Reply-To: <20010916155003.B1446@lucon.org>; from hjl@lucon.org on Sun, Sep 16, 2001 at 03:50:03PM -0700
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~
next prev parent reply other threads:[~2001-09-17 22:48 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 [this message]
2001-09-17 22:56 ` Jakub Jelinek
2001-09-20 22:52 ` Geoff Keating
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=20010917154754.E30386@redhat.com \
--to=rth@redhat.com \
--cc=binutils@sourceware.cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
--cc=rmurray@cyberhqz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.