linux-mips
[Top] [All Lists]

Re: Relocation problem with MIPS kernel modules

To: David Daney <ddaney@caviumnetworks.com>
Subject: Re: Relocation problem with MIPS kernel modules
From: Ralf Baechle <ralf@linux-mips.org>
Date: Mon, 3 Aug 2009 20:14:14 +0100
Cc: David VomLehn <dvomlehn@cisco.com>, GCC Help Mailing List <gcc-help@gcc.gnu.org>, Linux MIPS Mailing List <linux-mips@linux-mips.org>
In-reply-to: <4A773026.3030002@caviumnetworks.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20090730184923.GA27030@cuplxvomd02.corp.sa.net> <20090803092030.GB30431@linux-mips.org> <20090803181958.GA7009@cuplxvomd02.corp.sa.net> <4A773026.3030002@caviumnetworks.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.18 (2008-05-17)
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

<Prev in Thread] Current Thread [Next in Thread>