This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Why are there 2 continous R_MIPS_HI16 reloc entries in the ELF excutable?

From: Ian Lance Taylor <iant at google dot com>
To: "Pan ruochen" <panruochen at gmail dot com>
Cc: "Thiemo Seufer" <ths at networkno dot de>, binutils at sourceware dot org
Date: Thu, 14 Aug 2008 16:24:24 -0700
Subject: Re: Why are there 2 continous R_MIPS_HI16 reloc entries in the ELF excutable?
References: <af0faace0808130252x423d7a90h48f0a947b5e8600c@mail.gmail.com> <20080813102102.GA23445@networkno.de> <af0faace0808140132u28ea366cifcd4687c751e722f@mail.gmail.com>

"Pan ruochen" <panruochen@gmail.com> writes:

>> The GNU toolchain allows relaxed rules of R_MIPS_HI16/R_MIPS_LO16
>> as an extension. (This allows some optimizations which wouldn't be
>> possible otherwise.)
>>
>>
>> Thiemo
>>
>
> How should I handle the GNU extension then? Are there any document?

Compute R_MIPS_HI16 as usual.  For R_MIPS_LO16, use the addend from
the immediately preceding R_MIPS_HI16.

Ian

Follow-Ups:
- Re: Why are there 2 continous R_MIPS_HI16 reloc entries in the ELF excutable?
  - From: Richard Sandiford

References:
- Why are there 2 continous R_MIPS_HI16 reloc entries in the ELF excutable?
  - From: Pan ruochen
- Re: Why are there 2 continous R_MIPS_HI16 reloc entries in the ELF excutable?
  - From: Thiemo Seufer
- Re: Why are there 2 continous R_MIPS_HI16 reloc entries in the ELF excutable?
  - From: Pan ruochen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]