This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: ARM EABI v3
- From: Daniel Jacobowitz <drow at false dot org>
- To: Paul Brook <paul at codesourcery dot com>
- Cc: binutils at sources dot redhat dot com, Richard Earnshaw <rearnsha at arm dot com>
- Date: Tue, 23 Mar 2004 11:40:07 -0500
- Subject: Re: ARM EABI v3
- References: <200403231633.24235.paul@codesourcery.com>
On Tue, Mar 23, 2004 at 04:33:24PM +0000, Paul Brook wrote:
> The patch below adds basic binutils support for AAELF (EABI v3).
I'm curious...
> ! unsigned int flags = meabi_flags;
>
> ! switch (meabi_flags)
> {
> ! case EF_ARM_EABI_UNKNOWN:
> ! /* Set the flags in the private structure. */
> ! if (uses_apcs_26) flags |= F_APCS26;
> ! if (support_interwork) flags |= F_INTERWORK;
...
> + case EF_ARM_EABI_VER3:
> + /* No additional flags to set. */
> + break;
Is implementing the v3 EABI flag useful when it causes us to lose all
supplementary information about the object file, e.g. interworking, FP
format, etc? I assume the plan is to record at least some of this
information in the future, but this patch lets -meabi=3 produce
"compatible" object files that really can't be usefully linked
together.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer