glibc 2.28 release on August 1st and extended ABI freeze for ppc64le float128.

Carlos O'Donell carlos@redhat.com
Tue Jul 3 13:53:00 GMT 2018


On 07/02/2018 09:59 AM, Maciej W. Rozycki wrote:
> 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.

This is OK for 2.28.

>  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.

I have reviewed the thread between you and Florian and I agree that this
change can go into 2.28.

>  Shall I file a separate BZ just for this patch, with the milestone set 
> to 2.28?

Answered by Joseph.

-- 
Cheers,
Carlos.



More information about the Libc-alpha mailing list