This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: ARM BE8 linker support
- From: Paul Brook <paul at codesourcery dot com>
- To: Richard Earnshaw <rearnsha at arm dot com>
- Cc: binutils at sources dot redhat dot com,Mark Mitchell <mark at codesourcery dot com>
- Date: Thu, 1 Apr 2004 19:23:57 +0100
- Subject: Re: ARM BE8 linker support
- Organization: CodeSourcery
- References: <200404011132.i31BWjTB019645@pc960.cambridge.arm.com>
On Thursday 01 April 2004 12:32, Richard Earnshaw wrote:
> Paul,
>
> I've just realized that there are a couple of omissions from this patch
> (there's no need to back it out, but I think they would be best addressed
> while the patch is fresh in your mind):
>
> BE8 mode should really only be possible for EABI v3 or later images.
Ok. Does this include the GNU EABI? ie. should it be extended to include BE8?
> It ought to be possible to create a configuration where BE8 mode is the
> default (assuming a big-endian object file)...
Does this mean making a new pseudo-target, eg. armbe8-elf, in the same way we
have armeb-elf which defaults to be32 objects?
If this were gcc I'd probably suggest something equivalent to -mabi=, and the
associated --with-abi= configure switch. There doesn't seem to be the same
precedent for this in binutils/ld though.
> ...so it should also be possible to disable that behaviour by requesting a
> BE32 image.
Ok.
> I'm not sure if this can happen, but it shouldn't be possible to generate
> BE8 when doing a partial link.
We always generate pure endian (ie. be32 or le32) objects when doing a partial
link. Do we want a diagnostic if --be8 is specitied?
Paul