summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorMasahiro Yamada <masahiroy@kernel.org>2024-03-06 21:47:09 +0900
committerMasahiro Yamada <masahiroy@kernel.org>2024-03-11 17:31:41 +0900
commit44929bfaceaaa6a854ddc6df6de9433fab1eef92 (patch)
treeba14570c5c064a0df800b1496896fc8ac10133f4 /scripts
parente2bad142bb3de836c5fbb3dff704578f5a73d8e6 (diff)
downloadlinux-stable-44929bfaceaaa6a854ddc6df6de9433fab1eef92.tar.gz
linux-stable-44929bfaceaaa6a854ddc6df6de9433fab1eef92.tar.bz2
linux-stable-44929bfaceaaa6a854ddc6df6de9433fab1eef92.zip
kbuild: remove GCC's default -Wpacked-bitfield-compat flag
Commit 4a5838ad9d2d ("kbuild: Add extra gcc checks") added the -Wpacked-bitfield-compat flag, but there is no need to add it explicitly. GCC manual says: "This warning is enabled by default. Use -Wno-packed-bitfield-compat to disable this warning." The test code in the manual: struct foo { char a:4; char b:8; } __attribute__ ((packed)); ... emits "note: offset of packed bit-field ‘b’ has changed in GCC 4.4" without W=3. Let's remove it, as it is a default with GCC. Clang does not support this flag, so its removal will not affect Clang builds. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Reviewed-by: Nathan Chancellor <nathan@kernel.org>
Diffstat (limited to 'scripts')
-rw-r--r--scripts/Makefile.extrawarn1
1 files changed, 0 insertions, 1 deletions
diff --git a/scripts/Makefile.extrawarn b/scripts/Makefile.extrawarn
index 2f25a1de129d..3ce5d503a6da 100644
--- a/scripts/Makefile.extrawarn
+++ b/scripts/Makefile.extrawarn
@@ -187,7 +187,6 @@ KBUILD_CFLAGS += -Wpointer-arith
KBUILD_CFLAGS += -Wredundant-decls
KBUILD_CFLAGS += -Wsign-compare
KBUILD_CFLAGS += -Wswitch-default
-KBUILD_CFLAGS += $(call cc-option, -Wpacked-bitfield-compat)
KBUILD_CPPFLAGS += -DKBUILD_EXTRA_WARN3