From: Ingo Molnar <mingo@kernel.org>
To: Nick Terrell <terrelln@meta.com>
Cc: Michael Kelley <mhklinux@outlook.com>,
Ard Biesheuvel <ardb@kernel.org>,
"dsterba@suse.com" <dsterba@suse.com>,
"brgerst@gmail.com" <brgerst@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Compile problems w/gcc 9.4.0 in linux-next
Date: Tue, 25 Mar 2025 11:18:43 +0100 [thread overview]
Message-ID: <Z-KDA-yFUuNM6PSx@gmail.com> (raw)
In-Reply-To: <323A7651-9BD8-4C8B-8784-8C9DAEF5FC88@meta.com>
* Nick Terrell <terrelln@meta.com> wrote:
>
>
> > On Mar 21, 2025, at 8:16 AM, Michael Kelley <mhklinux@outlook.com> wrote:
> >
> > >
> > From: Ingo Molnar <mingo@kernel.org> Sent: Friday, March 21, 2025 12:38 AM
> >>
> >> * Michael Kelley <mhklinux@outlook.com> wrote:
> >>
> >>>> What are your thoughts as maintainers of lib/zstd?
> >>>
> >>> FYI, the same segfault occurs with gcc 10.5. The problem is fixed
> >>> in gcc 11.4.
> >>
> >> So the patch below would work this around on GCC9 and GCC10?
> >
> > I've confirmed that the patch gives a clean compile with gcc 9.4.
> >
> > Note that I confirmed yesterday that the gcc problem is fixed with
> > 11.4. I don't know about earlier gcc 11 minor versions. Lemme see
> > if I can get the original gcc 11 release and try that to confirm that
> > your patch has the right version cutoff.
>
> Thanks for the report & proposed fix!
>
> If you can test gcc-11.0, that would be great, otherwise we could just
> cut off at (__GNUC__ >= 12 || (__GNUC__ == 11 && __GNUC_MINOR__ >= 4))
>
> I am preparing the zstd-v1.5.7 update, and I will pull a patch that
> fixes this into my tree. If someone wants to submit a patch I'll pull
> that, otherwise I can submit one later today.
The proper cutoff would be GCC 11.1, not 11.4, as per the testing of
Michael Kelley, right?
Thanks,
Ingo
next prev parent reply other threads:[~2025-03-25 10:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 18:29 Compile problems w/gcc 9.4.0 in linux-next Michael Kelley
2025-03-20 19:19 ` Ard Biesheuvel
2025-03-20 20:41 ` Michael Kelley
2025-03-20 21:58 ` Michael Kelley
2025-03-21 7:38 ` Ingo Molnar
2025-03-21 15:16 ` Michael Kelley
2025-03-21 18:06 ` Nick Terrell
2025-03-25 10:18 ` Ingo Molnar [this message]
2025-03-25 20:47 ` Nick Terrell
2025-03-25 22:05 ` Ingo Molnar
2025-03-22 7:36 ` Ingo Molnar
2025-03-23 4:58 ` Nick Terrell
2025-03-23 17:52 ` Michael Kelley
2025-03-21 7:37 ` Ingo Molnar
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=Z-KDA-yFUuNM6PSx@gmail.com \
--to=mingo@kernel.org \
--cc=ardb@kernel.org \
--cc=brgerst@gmail.com \
--cc=dsterba@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=terrelln@meta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.