This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Patch 1 of 2 for ILP32 aarch64
- From: Steve Ellcey <sellcey at caviumnetworks dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Thu, 23 Feb 2017 14:14:26 -0800
- Subject: Re: [PATCH] Patch 1 of 2 for ILP32 aarch64
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Steve dot Ellcey at cavium dot com;
- References: <1487780940.2866.151.camel@caviumnetworks.com> <alpine.DEB.2.20.1702221700340.8704@digraph.polyomino.org.uk>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On Wed, 2017-02-22 at 17:01 +0000, Joseph Myers wrote:
> On Wed, 22 Feb 2017, Steve Ellcey wrote:
>
> >
> > This is the first of two aarch64 ILP32 patches. I think the only
> > blocker in checking these in is getting the ILP32 kernel changes
> > accepted and that is currently being worked on. In the meantime I
> > thought I would repost them because the previous patches do not apply
> > cleanly to the top-of-tree anymore and these will. This first patch is
> > just the abilist file changes. The version numbers are still at 2.25,
> > I don't know if that is going to change for the next glibc release but
> > this matches what is currently at top-of-tree.
> The next glibc release will be 2.26. All new ports and new symbols need
> to use version 2.26, not 2.25.
Is there something other than the abilist files that needs to be
changed from 2.25 to 2.26 with a new release? If I update
libc.abilist, etc. to have 2.26 instead of 2.25 and run the testsuite
all the check-abi-* tests fail because the generated symlist files
still have 2.25 in them. Is there some global 'version number'
somewhere that needs to be incremented from 2.25 to 2.26? If so, I
couldn't find it.
Steve Ellcey
sellcey@cavium.com