This is the mail archive of the
mailing list for the glibc project.
Re: ABI stability for AArch64 hard-float BE?
- From: Marcus Shawcroft <marcus dot shawcroft at gmail dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: Marcus Shawcroft <marcus dot shawcroft at linaro dot org>, GNU C Library <libc-alpha at sourceware dot org>, Richard Earnshaw <Richard dot Earnshaw at arm dot com>
- Date: Mon, 10 Feb 2014 11:11:02 +0000
- Subject: Re: ABI stability for AArch64 hard-float BE?
- Authentication-results: sourceware.org; auth=none
- References: <52EFCE6C dot 1040602 at redhat dot com>
On 3 February 2014 17:14, Carlos O'Donell <firstname.lastname@example.org> wrote:
> We list the AArch64 hard-float BE ABI in the
> official glibc ABI list here:
> Is that ABI considered stable?
The relevant PCS and ABI documents from ARM are out of draft status.
Linux kernel support for BE landed in 3.13 which was a few weeks back,
~ Jan 20th.
The last run for glibc BE regression I ran shortly after the loader
name change for BE was clean. However, I'm led to believe there are
issues high lighted in BE by the LTP test suite which are not present
My biggest concern with the BE linux toolchain as whole is that it is
immature and has had limited use. That said, with the BE loader name
now in place I am not aware of outstanding ABI issues and that it is
reasonable to assume the LP64 BE glibc ABI for aarch64 is stable.