From: Carlos O'Donell <carlos@redhat.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
Bill Schmidt <wschmidt@us.ibm.com>
Subject: Re: glibc 2.28 release on August 1st and extended ABI freeze for ppc64le float128.
Date: Tue, 03 Jul 2018 13:53:00 -0000 [thread overview]
Message-ID: <5b7c9599-4d02-27cd-6f55-a1224b6cdbd6@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1807021441011.20622@tp.orcam.me.uk>
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.
next prev parent reply other threads:[~2018-07-03 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 19:32 Carlos O'Donell
2018-06-26 19:35 ` Florian Weimer
2018-06-26 19:43 ` Tulio Magno Quites Machado Filho
2018-06-26 20:52 ` Joseph Myers
2018-06-27 2:00 ` Tulio Magno Quites Machado Filho
2018-06-29 14:33 ` Szabolcs Nagy
2018-06-29 14:36 ` Florian Weimer
2018-06-29 15:37 ` Szabolcs Nagy
2018-07-02 13:59 ` Maciej W. Rozycki
2018-07-02 15:22 ` Joseph Myers
2018-07-02 15:40 ` Maciej W. Rozycki
2018-07-03 13:53 ` Carlos O'Donell [this message]
2018-07-04 19:35 ` Tulio Magno Quites Machado Filho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b7c9599-4d02-27cd-6f55-a1224b6cdbd6@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=macro@mips.com \
--cc=tuliom@linux.vnet.ibm.com \
--cc=wschmidt@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).