Re: recent binutils and mips64-linux

[Thiemo Seufer <ica2_ts at csv dot ica dot uni-stuttgart dot de>]

Richard Sandiford wrote:
> "Maciej W. Rozycki" <macro@ds2.pg.gda.pl> writes:
> >  Note that the resulting object file should be somehow marked to let a
> > user know it has some addressing restrictions and cannot be linked at an
> > arbitrary address.
> 
> What sort marking would be best?  A fake section, like .gnu.mips.sym32?
> (suggestions for a better name welcome)  That's easy to do in gcc and
> wouldn't need any new as/ld flags.
> 
> Or should it be an ELF header flag?  A proper note section?

Header flags tend to create compatibility side effects, a note section
might be the best.

> An alternative (...idle thinking, probably a bad idea...) might be to
> add a new relocation type which is calculated like R_MIPS_HI16 but which
> complains about non-32bit addresses.  Then add a %reloc() operator for it.
> This'd definitely be more work though...

Sounds like overengineering to me. :-)


Thiemo