summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2020-05-10 00:40:52 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2020-05-10 00:40:52 +0200
commit5a76021c2eff7fcf2f0918a08fd8a37ce7922921 (patch)
tree96fb6bc668e9f84a946676df3afb10f4093000c4
parentgcc-10: disable 'array-bounds' warning for now (diff)
downloadlinux-5a76021c2eff7fcf2f0918a08fd8a37ce7922921.tar.xz
linux-5a76021c2eff7fcf2f0918a08fd8a37ce7922921.zip
gcc-10: disable 'stringop-overflow' warning for now
This is the final array bounds warning removal for gcc-10 for now. Again, the warning is good, and we should re-enable all these warnings when we have converted all the legacy array declaration cases to flexible arrays. But in the meantime, it's just noise. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-rw-r--r--Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/Makefile b/Makefile
index b4c88f0eb6fe..abdb355d3f46 100644
--- a/Makefile
+++ b/Makefile
@@ -880,6 +880,7 @@ KBUILD_CFLAGS += $(call cc-disable-warning, stringop-truncation)
# We'll want to enable this eventually, but it's not going away for 5.7 at least
KBUILD_CFLAGS += $(call cc-disable-warning, zero-length-bounds)
KBUILD_CFLAGS += $(call cc-disable-warning, array-bounds)
+KBUILD_CFLAGS += $(call cc-disable-warning, stringop-overflow)
# Enabled with W=2, disabled by default as noisy
KBUILD_CFLAGS += $(call cc-disable-warning, maybe-uninitialized)