This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [patch] MIPS: Follow the ABI rules for ordering HI16_S/LO16relocs
- From: Richard Sandiford <rsandifo at redhat dot com>
- To: "Maciej W. Rozycki" <macro at linux-mips dot org>
- Cc: binutils at sources dot redhat dot com
- Date: Tue, 29 Jun 2004 08:06:45 +0100
- Subject: Re: [patch] MIPS: Follow the ABI rules for ordering HI16_S/LO16relocs
- References: <Pine.LNX.4.55.0406281754480.23162@jurand.ds.pg.gda.pl>
"Maciej W. Rozycki" <macro@linux-mips.org> writes:
> This is one of the fortunate areas the MIPS ABI supplement is clear
> about. On page 4-18 of the spec, there is the following statement:
> "R_MIPS_LO16 entries without an R_MIPS_HI16 entry immediately preceding
> are orphaned and the previously defined R_MIPS_HI16 is used for computing
> the addend." The implication is for a correct calculation of the addend
> for a LO16 relocation, the corresponding HI16 relocation has to precede it
> with no other HI16 relocations inbetween.
But since the introduction of %lo(), we've always supported the case
in which one R_MIPS_HI16 has several R_MIPS_LO16s. As a GNU extension.
We shouldn't change that now.
Richard