From: Sunil Pandey <skpgkp2@gmail.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: glibc 2.36 release and branch freeze.
Date: Fri, 29 Jul 2022 08:31:44 -0700 [thread overview]
Message-ID: <CAMAf5_cc=7nX7xqmNz0RKR8AG_Gnu1Nj8W8-Mb73zYcx+nOaoQ@mail.gmail.com> (raw)
In-Reply-To: <2d344959-f446-5025-78d5-85f808bbea77@redhat.com>
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.
next prev parent reply other threads:[~2022-07-29 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 15:26 Carlos O'Donell
2022-07-29 15:31 ` Sunil Pandey [this message]
2022-07-29 15:46 ` Carlos O'Donell
2022-07-29 16:54 ` Yann Droneaud
2022-07-30 19:03 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMAf5_cc=7nX7xqmNz0RKR8AG_Gnu1Nj8W8-Mb73zYcx+nOaoQ@mail.gmail.com' \
--to=skpgkp2@gmail.com \
--cc=carlos@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).