This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.29 - Winter is coming...
- From: Szabolcs Nagy <Szabolcs dot Nagy at arm dot com>
- To: Siddhesh Poyarekar <siddhesh at gotplt dot org>, GLIBC Devel <libc-alpha at sourceware dot org>
- Cc: nd <nd at arm dot com>, Feng Xue <fxue at os dot amperecomputing dot com>
- Date: Tue, 8 Jan 2019 13:33:48 +0000
- Subject: Re: glibc 2.29 - Winter is coming...
- References: <833db514-f25e-0c41-bf06-b8cc9272f1c2@gotplt.org>
On 02/01/2019 10:28, Siddhesh Poyarekar wrote:
> Status of Release blockers:
>
> I have reviewed all original release blockers, including a couple of additional ones that got added later but I couldn't get to all of them. As
> of now, the pending blockers do not look suitable for inclusion at this stage and so will be deferred to 2.30 development.
i'd like to commit some patches that only affect aarch64
(and only particular uarches there):
memchr and memset for AmpereComputing emag (approved before freeze):
https://sourceware.org/ml/libc-alpha/2018-12/msg00626.html
https://sourceware.org/ml/libc-alpha/2018-12/msg00628.html
https://sourceware.org/ml/libc-alpha/2018-12/msg00820.html
ifunc for ares (does not add new implementation):
https://sourceware.org/ml/libc-alpha/2018-12/msg00754.html
these seem safer to me to commit now than to backport them
later and should not interfere with the glibc release process.