From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Michael Kelley <mhklinux@outlook.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: Fri, 21 Mar 2025 08:37:16 +0100 [thread overview]
Message-ID: <Z90XLMUzB25HpGcb@gmail.com> (raw)
In-Reply-To: <CAMj1kXH-awwT99FTaBJqyEbgBoxc20h4LfbzXMP00NQHBs03+A@mail.gmail.com>
* Ard Biesheuvel <ardb@kernel.org> wrote:
> > Interestingly, if DYNAMIC_BMI2 in
> > lib/zstd/common/portability_macros.h is changed on line 61 to
> > always be defined as 0, the compile problem in huf_compress.c goes
> > away.
>
> Without having looked at the crashing code, I suspect that the only
> meaningful course of action here is to tweak the conditional logic
> that defines DYNAMIC_BMI2 to only enable it for GCC >= 10.1 (assuming
> those are unaffected) In any case, GCC 9.4 is not going to get fixed
> in the field, so even if this gets fixed on the GCC side, we will
> have to deal with it here.
Apparently all GCC < 11.0 versions are crashing.
Would something like the fix below work?
Thanks,
Ingo
===============>
lib/zstd/common/portability_macros.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/zstd/common/portability_macros.h b/lib/zstd/common/portability_macros.h
index 0e3b2c0a527d..0dde8bf56595 100644
--- a/lib/zstd/common/portability_macros.h
+++ b/lib/zstd/common/portability_macros.h
@@ -55,7 +55,7 @@
#ifndef DYNAMIC_BMI2
#if ((defined(__clang__) && __has_attribute(__target__)) \
|| (defined(__GNUC__) \
- && (__GNUC__ >= 5 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 8)))) \
+ && (__GNUC__ >= 11))) \
&& (defined(__x86_64__) || defined(_M_X64)) \
&& !defined(__BMI2__)
# define DYNAMIC_BMI2 1
prev parent reply other threads:[~2025-03-21 7:37 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
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 [this message]
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=Z90XLMUzB25HpGcb@gmail.com \
--to=mingo@kernel.org \
--cc=ardb@kernel.org \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.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.