From: Ralf Baechle <ralf@uni-koblenz.de>
To: Mark Mitchell <mark@codesourcery.com>,
binutils@sourceware.cygnus.com, linux@cthulhu.engr.sgi.com,
linux-mips@fnet.fr, linux-mips@vger.rutgers.edu
Subject: HI16 / LO16 relocations.
Date: Wed, 4 Aug 1999 00:09:08 +0200 [thread overview]
Message-ID: <19990804000908.A7145@uni-koblenz.de> (raw)
Mark, for now I'm just posting this in the hope it may ring a bell.
It seems like HI16 / LO16 relocation pairs are not handled correctly
This may result in ``la $reg, symbol'' ending up after the final link
as ``la $reg, symbol + 0x10000''.
I'll try to come up with a resonably small example tomorrow; right now
I've just discovered this problem and can only show the problem in
the diffs of disassembler listings between the two builds of a Linux
kernel with binutils 2.8.1 and cvs-binutils.
Ralf
next reply other threads:[~1999-08-03 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-03 22:09 Ralf Baechle [this message]
[not found] ` <19990803154236N.mitchell@codesourcery.com>
1999-08-03 23:01 ` HI16 / LO16 relocations 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=19990804000908.A7145@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=binutils@sourceware.cygnus.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.com \
--cc=mark@codesourcery.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