From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: David VomLehn <dvomlehn@cisco.com>,
GCC Help Mailing List <gcc-help@gcc.gnu.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: Relocation problem with MIPS kernel modules
Date: Mon, 3 Aug 2009 20:14:14 +0100 [thread overview]
Message-ID: <20090803191413.GA22543@linux-mips.org> (raw)
In-Reply-To: <4A773026.3030002@caviumnetworks.com>
On Mon, Aug 03, 2009 at 11:44:54AM -0700, David Daney wrote:
>>> R_MIPS_HI16 relocations to be followed by a R_MIPS_LO16 symbol. All
>>> relocations of this sequence must use the same symbol, of course. This is
>>> a very old extension; I think it predates the Linux/MIPS port.
>>
>> Perhaps a foolish question, but is this documented anywhere?
>
> What more documentation do you need? It's obvious if you read
> bfd/elf{32,64,xx}-mips.c :-).
David ist (unforutunately ...) right. I don't think this is documented
anywhere. I also only learned it from reading the binutils sources.
Ralf
next prev parent reply other threads:[~2009-08-03 19:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 18:49 Relocation problem with MIPS kernel modules David VomLehn
2009-07-30 19:15 ` David Daney
2009-07-30 21:26 ` David VomLehn
2009-08-03 9:20 ` Ralf Baechle
2009-08-03 18:19 ` David VomLehn
2009-08-03 18:44 ` David Daney
2009-08-03 19:14 ` Ralf Baechle [this message]
2009-08-07 6:38 ` Marshall B. Rogers
2009-08-03 19:33 ` David Daney
2009-08-03 20:15 ` David VomLehn
2009-08-03 23:55 ` Ralf Baechle
2009-08-04 2:18 ` David VomLehn
2009-08-07 15:29 ` Maciej W. Rozycki
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=20090803191413.GA22543@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=dvomlehn@cisco.com \
--cc=gcc-help@gcc.gnu.org \
--cc=linux-mips@linux-mips.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 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.