From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 2.6.6] Workaround linker bug
Date: Sat, 05 Jun 2004 04:18:14 +0000 [thread overview]
Message-ID: <16577.18822.988624.4464@napali.hpl.hp.com> (raw)
In-Reply-To: <9422.1085636381@kao2.melbourne.sgi.com>
>>>>> On Thu, 27 May 2004 15:39:41 +1000, Keith Owens <kaos@sgi.com> said:
Keith> Building 2.6.6-ia64-040521, using GNU ld version 2.14.90.0.4
Keith> 20030523. __gp is sometimes set incorrectly. Instead of
Keith> being .got + 0x2000000, it is set to .data + 0x2000000, which
Keith> breaks some LTOFF22 and GPREL22 entries.
Keith> This is non-deterministic, changing the path name to the
Keith> kernel tree which changes the size of some messages in .data
Keith> is enough to make the linker get it right. Force __gp to be
Keith> based on .got.
I can't say I have seen this myself, but the workaround is sensible enough,
so I applied the patch.
Thanks, and sorry for the delay (still working through my backlog...).
--david
prev parent reply other threads:[~2004-06-05 4:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 5:39 [patch 2.6.6] Workaround linker bug Keith Owens
2004-05-27 7:08 ` H. J. Lu
2004-06-05 4:18 ` David Mosberger [this message]
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=16577.18822.988624.4464@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.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