glibc 2.31: hard freeze on Friday, 31st Jan

[Carlos O'Donell]

On 1/31/20 10:06 AM, Siddhesh Poyarekar wrote:
> On 31/01/20 17:03, Adhemerval Zanella wrote:
>> Based on the extended asm and local register variable usage with GCC on
>> the 'powerpc Linux scv support and scv system call ABI proposal' I think
>> we hit a nasty latent sparc issue I am seeing at least on sparc32 tests
>> (it clobbers the syscalls result and make some calls to clock_nanosleep
>> to not act as a cancellation entrypoint).
>>
>> I am working on a solution, do you think we should push it after the
>> release branch is created or can we hold a day or two?
> 
> I see that this is documented in the 2.31 wiki, I think that's a
> reasonable compromise given the stage we're in.  Lets stik to schedule
> and backport once there's consensus on the fix.

Agreed.

The sparc32 issue, while a regression, is not a blocker for the release.

We should document the regression and alert downstream that a fix is in progress.

-- 
Cheers,
Carlos.