This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: AArch64 ILP32 abi in glibc
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>, Joseph Myers <joseph at codesourcery dot com>
- Cc: Szabolcs Nagy <szabolcs dot nagy at arm dot com>, GNU C Library <libc-alpha at sourceware dot org>, nd at arm dot com, Marcus Shawcroft <Marcus dot Shawcroft at arm dot com>, Ramana Radhakrishnan <Ramana dot Radhakrishnan at arm dot com>, Catalin Marinas <catalin dot marinas at arm dot com>, Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, Steve Ellcey <sellcey at caviumnetworks dot com>, Andrew Pinski <pinskia at gmail dot com>
- Date: Thu, 27 Jul 2017 09:13:11 -0400
- Subject: Re: AArch64 ILP32 abi in glibc
- Authentication-results: sourceware.org; auth=none
- References: <59553555.3010004@arm.com> <1e2219c7-6ff1-2ba7-d6b0-bbfe84ac2865@redhat.com> <alpine.DEB.2.20.1707071507230.28054@digraph.polyomino.org.uk> <f2f9f772-1b7a-482b-b3cf-d0c578ece129@redhat.com>
On 07/27/2017 03:49 AM, Florian Weimer wrote:
> On 07/07/2017 05:08 PM, Joseph Myers wrote:
>> On Fri, 7 Jul 2017, Florian Weimer wrote:
>>
>>> Can we do without a branch instead? I don't see how things are simpler
>>> for non-ILP32 developers without the branch. I expected that I'll deal
>>
>> I think any port in master should build with mainline upstream kernel
>> headers (and other components), or at least a kernel port we can be
>> confident will be upstream in the next release or two.
>
> My comments were based on the Hurd and NaCl experiences. I don't want
> another port which is effectively out of tree, but with an expectation
> to keep things going there. If we can pretend that the port does not
> exist, that's fine, but why would we coordinate this matter on
> libc-alpha if that's the goal?
To set clear expectations.
To avoid people like you and I wondering if we need to do anything special
for the ARM vendor branch.
To describe the long term goal of merging the branch in the future.
As a volunteer you are free to *help* maintain that ILP32 branch if
you so choose.
All of these things are an important part of clear and open communication.
At this point you can ignore the branch in good conscience and focus on those
things that are important for you.
--
Cheers,
Carlos.