This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Update on freeze status of glibc 2.18?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, Ryan Arnold <rsa at us dot ibm dot com>, Siddhesh Poyarekar <siddhesh at redhat dot com>
- Date: Tue, 11 Jun 2013 17:00:32 -0400
- Subject: Re: Update on freeze status of glibc 2.18?
- References: <51B65DE4 dot 4010107 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1306111716480 dot 29045 at digraph dot polyomino dot org dot uk>
On 06/11/2013 01:20 PM, Joseph S. Myers wrote:
> On Mon, 10 Jun 2013, Carlos O'Donell wrote:
>
>> I see you checking in more fixes to libm testing, are these
>> things you want in 2.18?
>
> I don't think it's particularly important which libm testsuite fixes end
> up in 2.18. As regards fixes to make tests handle better cases where
> exceptions / rounding modes are defined in the headers but may not be
> supported at runtime, most of those should be safe during the freeze
> anyway. But getting fully clean expected test results on more
> configurations (which is the point there - reducing the set of failures
> someone testing on soft-float ARM or MIPS needs to know to expect) is a
> fairly long-term goal.
Agreed. I just didn't want to declare a freeze if you still had something
you wanted in 2.18.
Thank you for clarifying.
Cheers,
Carlos.