This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: 2.26 release blockers?
- From: Siddhesh Poyarekar <siddhesh at gotplt dot org>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, libc-alpha at sourceware dot org
- Date: Wed, 5 Jul 2017 09:08:28 +0530
- Subject: Re: 2.26 release blockers?
- Authentication-results: sourceware.org; auth=none
- References: <6ce02dfc-d8e8-bcd8-4ced-a09293cf1732@redhat.com> <8bcba445-524d-c0b2-cd11-03ef82f3f5a5@linaro.org> <1065eb07-b190-6edd-fc53-a717569a2273@gotplt.org> <alpine.DEB.2.20.1707041944400.14976@digraph.polyomino.org.uk>
On Wednesday 05 July 2017 01:16 AM, Joseph Myers wrote:
> Adding new symbols to the ABI - anything involving architecture-specific
> sysdeps changes - *is* affecting architecture testing. In this case
Oh yes, I acknowledge that.
> there's also the possibility of interactions with the thread types
> headers, if there's anything in the architecture-specific headers that
> works for pthreads but not for C11 threads.
>From a quick look at the changes, I couldn't find any changes in the
arch-specific sysdeps directories other than the abilist changes, i.e.
there are no architecture-specific headers. Bugs in C11 should thus be
limited to C11 and not creep into nptl and definitely remain in the
generic scope.
So my argument is that a trivial addition of new symbols should have
minimal effect on architecture-specific testing given that there is no
other change.
Siddhesh