On Mon, Feb 28, 2022 at 12:57:55PM +0100, Arnd Bergmann wrote: > On Mon, Feb 28, 2022 at 12:47 PM Marco Elver <elver@xxxxxxxxxx> wrote: > > On Mon, 28 Feb 2022 at 11:32, Arnd Bergmann <arnd@xxxxxxxxxx> wrote: > > > > > Nathan Chancellor reported an additional -Wdeclaration-after-statement > > > warning that appears in a system header on arm, this still needs a > > > workaround. > > > > On the topic of Wdeclaration-after-statement, Clang only respects this > > warning with C99 and later starting with Clang 14: > > https://github.com/llvm/llvm-project/commit/c65186c89f35#diff-ec770381d76c859f5f572db789175fe44410a72608f58ad5dbb14335ba56eb97R61 > > > > Until Clang 14, -Wdeclaration-after-statement is ignored by Clang in > > newer standards. If this is a big problem, we can probably convince > > the Clang stable folks to backport the fixes. However, the build won't > > fail, folks might just miss the warning if they don't also test with > > GCC. Unfortunately, none of the branches prior to release/14.x are going to see any more updates (at least as far as I am aware, as the LLVM community only supports one release branch at a time) but as Arnd mentioned below, I do not really see that as a problem, as newer versions of clang and GCC will catch these warnings. > I don't expect this is to be a big issue, as long as the latest clang behaves > as expected. There are many warnings that are only produced by one of the > two compilers, so this is something we already deal with. > > I think it's more important to address the extra warning that Nathan > reported, where clang now complains about the intermingled declaration > in a system header when previously neither gcc nor clang noticed this. Right. Based on the upstream LLVM bug, I think we should just fix arm_neon.h to avoid triggering -Wdeclaration-after-statement to have something that is (hopefully) relatively low risk for a clang-14 backport, rather than addressing the root cause of clang warning in system macros, as it sounds like fixing that has some risks that are not fully understood at this point. The kernel only uses very specific system headers after commit 04e85bbf71c9 ("isystem: delete global -isystem compile option"), so I don't think that my suggested approach will have many downsides. I think I see how to potentially fix arm_neon.h in clang/utils/TableGen/NeonEmitter.cpp, I just have to think about it a little more. Realistically, I don't think special casing this in lib/raid6 is the end of the world: diff --git a/lib/raid6/Makefile b/lib/raid6/Makefile index 45e17619422b..a41ff71b90af 100644 --- a/lib/raid6/Makefile +++ b/lib/raid6/Makefile @@ -38,6 +38,10 @@ ifeq ($(CONFIG_KERNEL_MODE_NEON),y) NEON_FLAGS := -ffreestanding # Enable <arm_neon.h> NEON_FLAGS += -isystem $(shell $(CC) -print-file-name=include) +# https://github.com/ClangBuiltLinux/linux/issues/1603 +ifeq ($(CONFIG_CC_IS_CLANG)$(CONFIG_CPU_BIG_ENDIAN),yy) +NEON_FLAGS += -Wno-declaration-after-statement +endif ifeq ($(ARCH),arm) NEON_FLAGS += -march=armv7-a -mfloat-abi=softfp -mfpu=neon endif > > > The differences between gnu99, gnu11, gnu1x and gnu17 are fairly > > > minimal and mainly impact warnings at the -Wpedantic level that the > > > kernel never enables. Between these, gnu11 is the newest version > > > that is supported by all supported compiler versions, though it is > > > only the default on gcc-5, while all other supported versions of > > > gcc or clang default to gnu1x/gnu17. > > > > > > Link: https://lore.kernel.org/lkml/CAHk-=wiyCH7xeHcmiFJ-YgXUy2Jaj7pnkdKpcovt8fYbVFW3TA@xxxxxxxxxxxxxx/ > > > Link: https://github.com/ClangBuiltLinux/linux/issues/1603 > > > Suggested-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> > > > Cc: Masahiro Yamada <masahiroy@xxxxxxxxxx> > > > Cc: linux-kbuild@xxxxxxxxxxxxxxx > > > Cc: llvm@xxxxxxxxxxxxxxx > > > Signed-off-by: Arnd Bergmann <arnd@xxxxxxxx> > > > > Acked-by: Marco Elver <elver@xxxxxxxxxx> Cheers, Nathan
