From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ld --relax, yet still: "relocation truncated to fit: PCREL21B" or "can't relax sect
Date: Wed, 10 Jan 2001 00:43:20 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205905@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205873@msgid-missing>
>| ./Tjdb-interp2/O.ia64-linux_n/plo_0.o: In function `func1':
>| ./Tjdb-interp2/O.ia64-linux_n/plo_0.o(.text+0x1046862): relocation truncated to fit: PCREL21B func2
>| ...
>| collect2: ld returned 1 exit status
Do you have a testcase I can look at? As far as I know, --relax still works.
This problem happens when you are calling a function that is too far away
for the offset in a br.call instruction. Or jumping to a branch that is too
far away. This could be a toolchain bug, or it could be a problem with the
program.
>| /usr/bin/ld: can't relax section: No such file or directory
>| collect2: ld returned 1 exit status
This was a temporary problem. It occurs if you have a toolchain with Richard
Henderson's 2000-10-09 bfd patch for sorting unwind sections, but don't have
his 2000-10-24 bfd patch which makes it work. I never released a toolchain
with the first patch but not the second. Perhaps you got a toolchain from
someone else? Or maybe you applied random patches from some mailing list
to your toolchain?
> gcc version 2.96-ia64-000717 snap 000925
> GNU ld version 2.9-ia64-000717 (with BFD 2.9-ia64-000717))
This is 2 months obsolete. The 001117 snapshot should be used instead of this
one.
Jim
next prev parent reply other threads:[~2001-01-10 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 14:47 [Linux-ia64] ld --relax, yet still: "relocation truncated to fit: PCREL21B" or "can't relax section" Steve Tynor
2001-01-10 0:43 ` Jim Wilson [this message]
2001-01-10 0:58 ` [Linux-ia64] ld --relax, yet still: "relocation truncated to fit: PCREL21B" or "can't relax sect Steve Tynor
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=marc-linux-ia64-105590678205905@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.org \
/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