glibc 2.22 --- We are in slushy freeze mode.

Carlos O'Donell carlos@redhat.com
Wed Jul 8 20:06:00 GMT 2015


On 07/08/2015 03:41 PM, H.J. Lu wrote:
> On Wed, Jul 8, 2015 at 10:16 AM, Carlos O'Donell <carlos@redhat.com> wrote:
>> On 07/08/2015 12:57 PM, H.J. Lu wrote:
>>> On Tue, Jul 7, 2015 at 11:32 AM, Carlos O'Donell <carlos@redhat.com> wrote:
>>>> We are now in slushy freeze mode. Please do not commit new features.
>>>> Please checkin new features which have been reviewed and are OK.
>>>> If your new feature still needs review it is too late now. Please
>>>> defer to glibc 2.23 when it opens.
>>>>
>>>> Documentation changes and bug fixes are still OK.
>>>
>>> Has anyone else seen this on i686:
>>>
>>> https://sourceware.org/bugzilla/show_bug.cgi?id=18645
>>>
>>
>> Try reverting ed225df3ad9cbac3c22ec3f0fbbed1f9c61d1c54 ?
>> We are discussing that it need to be reverted because of some
>> of the complications it causes internally with glibc.
>>
> 
> It doesn't help.
> 

Yes, the failure looks like it's been there for longer than
Martin's patch.

In 2.21 it shows up for 64/32-bit tile and 32-bit hppa.

I did the x86 32-bit testing for the 2.21 release on an
f21 box and the combination there didn't cause it to show up.

Cheers,
Carlos.



More information about the Libc-alpha mailing list