This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.28 release on August 1st and extended ABI freeze for ppc64le float128.
- From: "Maciej W. Rozycki" <macro at mips dot com>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>, Bill Schmidt <wschmidt at us dot ibm dot com>
- Date: Mon, 2 Jul 2018 14:59:06 +0100
- Subject: Re: glibc 2.28 release on August 1st and extended ABI freeze for ppc64le float128.
- References: <4db8730d-158c-67e4-b4fd-55b3cc9a7100@redhat.com>
On Tue, 26 Jun 2018, Carlos O'Donell wrote:
> I'm not suggesting we move the August 1st release, but just decrease
> the window of the ABI/API freeze, and restrict it to only the changes
> we accept as such e.g. ppc64le float128 changes.
Can I have:
<https://patchwork.sourceware.org/patch/27910/>
<https://sourceware.org/ml/libc-alpha/2018-06/msg00511.html>
decided for 2.28? Unfortunately I only discovered it so late in the
development cycle, because I have only recently dived into addressing
binutils PR ld/21375 and discovered BZ #23307 in the course.
The patch blocks the fix for PR ld/21375, and it will probably make no
sense once we have a release with absolute symbols working (BZ #19818 + BZ
#23307), but no ABI marking for that. So I think it's a 2.28-or-never
change. The linker-side fix is scheduled for Jan 2019 binutils release.
Shall I file a separate BZ just for this patch, with the milestone set
to 2.28?
Maciej