glibc 2.36 release and branch freeze.

glibc 2.36 release and branch freeze.

[Carlos O'Donell]

Community,

The branch is officially frozen. Please check with the RM before committing
anything to the branch.

I'm the current RM. Please TO: me if you want my attention for a commit that
needs inclusion before we cut the release.

I want to thank Adhemerval Zanella for stepping in to help as RM and working
with the community on the arc4random() changes and the LoongArch commits.
Thank you Adhemerval!

I see at least two compile related issues, one that might block the relase,
but I need to confirm them. I'd like to make sure that glibc 2.36 builds
with vanilla gcc 12, but I see a Fedora 36 + gcc 12 related failure:
https://sourceware.org/pipermail/libc-alpha/2022-July/141127.html

Sunil, HJ,

I also see a gcc 6 related failure reported by Sunil here:
https://sourceware.org/pipermail/libc-alpha/2022-July/140500.html

Do we have a workaround for that issue? We document gcc 6.2 as the minimum
build requirement. Does that need to be raised?

-- 
Cheers,
Carlos.

Re: glibc 2.36 release and branch freeze.

[Sunil Pandey]

On Fri, Jul 29, 2022 at 8:26 AM Carlos O'Donell <carlos@redhat.com> wrote:
>
> Community,
>
> The branch is officially frozen. Please check with the RM before committing
> anything to the branch.
>
> I'm the current RM. Please TO: me if you want my attention for a commit that
> needs inclusion before we cut the release.
>
> I want to thank Adhemerval Zanella for stepping in to help as RM and working
> with the community on the arc4random() changes and the LoongArch commits.
> Thank you Adhemerval!
>
> I see at least two compile related issues, one that might block the relase,
> but I need to confirm them. I'd like to make sure that glibc 2.36 builds
> with vanilla gcc 12, but I see a Fedora 36 + gcc 12 related failure:
> https://sourceware.org/pipermail/libc-alpha/2022-July/141127.html
>
> Sunil, HJ,
>
> I also see a gcc 6 related failure reported by Sunil here:
> https://sourceware.org/pipermail/libc-alpha/2022-July/140500.html
>
> Do we have a workaround for that issue? We document gcc 6.2 as the minimum
> build requirement. Does that need to be raised?
>
> --
> Cheers,
> Carlos.
>

gcc6 related build failure fixed by the following commit.

commit f2698954ff9c2f9626d4bcb5a30eb5729714e0b0
Author: Noah Goldstein <goldstein.w.n@gmail.com>
Date:   Tue Jul 12 11:48:04 2022 -0700

    x86: Remove __mmask intrinsics in strstr-avx512.c

    The intrinsics are not available before GCC7 and using standard
    operators generates code of equivalent or better quality.

Re: glibc 2.36 release and branch freeze.

[Carlos O'Donell]

On 7/29/22 11:31, Sunil Pandey wrote:
> On Fri, Jul 29, 2022 at 8:26 AM Carlos O'Donell <carlos@redhat.com> wrote:
>>
>> Community,
>>
>> The branch is officially frozen. Please check with the RM before committing
>> anything to the branch.
>>
>> I'm the current RM. Please TO: me if you want my attention for a commit that
>> needs inclusion before we cut the release.
>>
>> I want to thank Adhemerval Zanella for stepping in to help as RM and working
>> with the community on the arc4random() changes and the LoongArch commits.
>> Thank you Adhemerval!
>>
>> I see at least two compile related issues, one that might block the relase,
>> but I need to confirm them. I'd like to make sure that glibc 2.36 builds
>> with vanilla gcc 12, but I see a Fedora 36 + gcc 12 related failure:
>> https://sourceware.org/pipermail/libc-alpha/2022-July/141127.html
>>
>> Sunil, HJ,
>>
>> I also see a gcc 6 related failure reported by Sunil here:
>> https://sourceware.org/pipermail/libc-alpha/2022-July/140500.html
>>
>> Do we have a workaround for that issue? We document gcc 6.2 as the minimum
>> build requirement. Does that need to be raised?
>>
>> --
>> Cheers,
>> Carlos.
>>
> 
> gcc6 related build failure fixed by the following commit.
> 
> commit f2698954ff9c2f9626d4bcb5a30eb5729714e0b0
> Author: Noah Goldstein <goldstein.w.n@gmail.com>
> Date:   Tue Jul 12 11:48:04 2022 -0700
> 
>     x86: Remove __mmask intrinsics in strstr-avx512.c
> 
>     The intrinsics are not available before GCC7 and using standard
>     operators generates code of equivalent or better quality.
> 

Perfect. Thanks!

-- 
Cheers,
Carlos.

Re: glibc 2.36 release and branch freeze.

[Yann Droneaud]

Hi,

Le 29/07/2022 à 17:26, Carlos O'Donell via Libc-alpha a écrit :
> Community,
>
> The branch is officially frozen. Please check with the RM before committing
> anything to the branch.
>
> I'm the current RM. Please TO: me if you want my attention for a commit that
> needs inclusion before we cut the release.

Patch "stdlib: Simplify arc4random_uniform" is not committed yet, but 
should be part of arc4random effort

https://sourceware.org/pipermail/libc-alpha/2022-July/141122.html
https://patchwork.sourceware.org/project/glibc/patch/20220729123211.876374-1-adhemerval.zanella@linaro.org/

Regards.
-- 
Yann Droneaud
OPTEYA

Re: glibc 2.36 release and branch freeze.

[Carlos O'Donell]

On 7/29/22 12:54, Yann Droneaud wrote:
> Hi,
> 
> Le 29/07/2022 à 17:26, Carlos O'Donell via Libc-alpha a écrit :
>> Community,
>>
>> The branch is officially frozen. Please check with the RM before committing
>> anything to the branch.
>>
>> I'm the current RM. Please TO: me if you want my attention for a commit that
>> needs inclusion before we cut the release.
> 
> Patch "stdlib: Simplify arc4random_uniform" is not committed yet, but should be part of arc4random effort
> 
> https://sourceware.org/pipermail/libc-alpha/2022-July/141122.html
> https://patchwork.sourceware.org/project/glibc/patch/20220729123211.876374-1-adhemerval.zanella@linaro.org/

It doesn't block the release, and we can commit it in 2.37 and backport if
we don't find any issues.

-- 
Cheers,
Carlos.