From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: "# 3.4.x" <stable@vger.kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"Justin M. Forbes" <jforbes@fedoraproject.org>,
Arnd Bergmann <arnd@kernel.org>, Nicolas Pitre <nico@linaro.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH] ARM: crypto: comment out gcc warning that breaks clang builds
Date: Mon, 1 Aug 2022 10:38:05 +0200 [thread overview]
Message-ID: <YueQ7eokc5DbbdTk@kroah.com> (raw)
In-Reply-To: <CAMj1kXFODDitAF+_UjrPeyV-tdAYv2n=8+hpXcQM4606ygiw=w@mail.gmail.com>
On Sun, Jul 31, 2022 at 01:13:14PM +0200, Ard Biesheuvel wrote:
> On Sun, 31 Jul 2022 at 12:39, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Sun, Jul 31, 2022 at 12:17:40PM +0200, Ard Biesheuvel wrote:
> > > On Sun, 31 Jul 2022 at 12:05, Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > >
> > > > The gcc build warning prevents all clang-built kernels from working
> > > > properly, so comment it out to fix the build.
> > > >
> > > > This is a -stable kernel only patch for now, it will be resolved
> > > > differently in mainline releases in the future.
> > > >
> > > > Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
> > > > Cc: "Justin M. Forbes" <jforbes@fedoraproject.org>
> > > > Cc: Ard Biesheuvel <ardb@kernel.org>
> > > > Cc: Arnd Bergmann <arnd@kernel.org>
> > > > Cc: Nicolas Pitre <nico@linaro.org>
> > > > Cc: Nathan Chancellor <nathan@kernel.org>
> > > > Cc: Nick Desaulniers <ndesaulniers@google.com>
> > > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > ---
> > > > arch/arm/lib/xor-neon.c | 3 ++-
> > > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/arch/arm/lib/xor-neon.c b/arch/arm/lib/xor-neon.c
> > > > index b99dd8e1c93f..7ba6cf826162 100644
> > > > --- a/arch/arm/lib/xor-neon.c
> > > > +++ b/arch/arm/lib/xor-neon.c
> > > > @@ -26,8 +26,9 @@ MODULE_LICENSE("GPL");
> > > > * While older versions of GCC do not generate incorrect code, they fail to
> > > > * recognize the parallel nature of these functions, and emit plain ARM code,
> > > > * which is known to be slower than the optimized ARM code in asm-arm/xor.h.
> > > > + *
> > > > + * #warning This code requires at least version 4.6 of GCC
> > > > */
> > > > -#warning This code requires at least version 4.6 of GCC
> > > > #endif
> > > >
> > > > #pragma GCC diagnostic ignored "-Wunused-variable"
> > >
> > > LGTM but doesn't Clang also complain about the GCC specific pragma?
> >
> > I don't know, all clang builds always failed at the first #warning line :)
>
> Just tried it, and it appears to ignore the #pragma so we're all good.
Wonderful, thanks for testing.
greg k-h
next prev parent reply other threads:[~2022-08-01 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 10:05 [PATCH] ARM: crypto: comment out gcc warning that breaks clang builds Greg Kroah-Hartman
2022-07-31 10:17 ` Ard Biesheuvel
2022-07-31 10:39 ` Greg Kroah-Hartman
2022-07-31 11:13 ` Ard Biesheuvel
2022-08-01 8:38 ` Greg Kroah-Hartman [this message]
2022-07-31 11:22 ` Arnd Bergmann
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=YueQ7eokc5DbbdTk@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=arnd@kernel.org \
--cc=jforbes@fedoraproject.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nico@linaro.org \
--cc=stable@vger.kernel.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