This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: recent binutils and mips64-linux
- From: Richard Sandiford <rsandifo at redhat dot com>
- To: "Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>
- Cc: Eric Christopher <echristo at redhat dot com>, cgd at broadcom dot com, binutils at sources dot redhat dot com
- Date: 02 Oct 2003 20:02:32 +0100
- Subject: Re: recent binutils and mips64-linux
- References: <Pine.GSO.3.96.1031002200639.15189G-100000@delta.ds2.pg.gda.pl>
"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?
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...
Richard