Machine testing for 2.39 !

[Adhemerval Zanella Netto]

Hi Andreas,

Would be ok to install the recent sparc fixes from Daniel Cederman? It
fixes some long standing issues on sparcv9 and I have another fix similar
to the 'signal return stub' one [2] for sparc64 that fixes other long
standing issues?

All the patches only affect sparc, so they should not interfere with the
other machine testing.

[1] https://patchwork.sourceware.org/project/glibc/list/?submitter=35381
[2] https://patchwork.sourceware.org/project/glibc/patch/20240112092628.2464455-6-cederman@gaisler.com/

On 15/01/24 17:52, Andreas K. Huettel wrote:
> It's time for machine testing (and collecting the results on the wiki)!
> https://sourceware.org/glibc/wiki/Release/2.39#Build_and_test_results
> 
> Cheers & saluti da Roma!
> Andreas
> 
> 
> Am Freitag, 12. Januar 2024, 23:21:31 CET schrieb Andreas K. Huettel:
>>>>
>>>> We follow for the upcoming glibc 2.39 the same schedule as usual.
>>>>
>>>> - January 12-31, "hard ABI freeze"
>>>>   * Noncritical bug fixes.
>>>>   * No ABI changes without RM discussion.
>>>>   * High risk bug fixes should be discussed on the list.
>>>
>>> Going through the mailing list I've come across the following unresolved threads.
>>> Please have a look. Comments welcome. 
>>>
>>> I'm on vacation travelling next week (Sun-Sat), which means limited e-mail access.
>>>
>>
>> Most items are now either pushed or explicitly postponed. Here's what's left:
>>
>> [PATCH] stdlib: Reinstate stable mergesort implementation on qsort
>> https://patchwork.sourceware.org/project/glibc/list/?series=29636
>> got some minor comments, but otherwise good to go
>>
>> [PATCH v2] x86-64: Check if mprotect works before rewriting PLT
>> https://patchwork.sourceware.org/project/glibc/list/?series=29649
>> needs review and push
>>
>> Once these two are in we can start machine testing. \o/
>>
>>
> 
>