From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5896 invoked by alias); 2 Jul 2018 13:59:35 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 5887 invoked by uid 89); 2 Jul 2018 13:59:35 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=August, carlos, august, Carlos X-HELO: 9pmail.ess.barracuda.com Date: Mon, 02 Jul 2018 13:59:00 -0000 From: "Maciej W. Rozycki" To: Carlos O'Donell CC: GNU C Library , Tulio Magno Quites Machado Filho , Bill Schmidt Subject: Re: glibc 2.28 release on August 1st and extended ABI freeze for ppc64le float128. In-Reply-To: <4db8730d-158c-67e4-b4fd-55b3cc9a7100@redhat.com> Message-ID: References: <4db8730d-158c-67e4-b4fd-55b3cc9a7100@redhat.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-Path: macro@mips.com X-BESS-Apparent-Source-IP: 12.201.5.32 X-SW-Source: 2018-07/txt/msg00020.txt.bz2 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: 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