diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-10-02 10:32:23 +0900 |
---|---|---|
committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-10-19 09:47:45 +0900 |
commit | 9df3e7a7d7d6d92df7c58fb17f900fdc2d8b5031 (patch) | |
tree | c955f868592d410173aa0ae96ce40c6b501dcccb /Makefile | |
parent | a33e7ae295d5bc20568c48ac217d07f011091c32 (diff) | |
download | linux-9df3e7a7d7d6d92df7c58fb17f900fdc2d8b5031.tar.gz linux-9df3e7a7d7d6d92df7c58fb17f900fdc2d8b5031.tar.bz2 linux-9df3e7a7d7d6d92df7c58fb17f900fdc2d8b5031.zip |
kbuild: add -Wno-unused-but-set-variable flag unconditionally
We have raised the compiler requirement from time to time.
With commit cafa0010cd51 ("Raise the minimum required gcc version
to 4.6"), the minimum for GCC is 4.6 now.
This flag was added by GCC 4.6, and it is recognized by ICC as well.
It is true that Clang does not support this flag but this commit is
just touching the else part of the "ifeq ($(cc-name),clang)" check.
Hence, Clang build is not affected.
Let's rip off the cc-disable-warning switch, and see if somebody
complains about it.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Diffstat (limited to 'Makefile')
-rw-r--r-- | Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -723,7 +723,7 @@ else # These warnings generated too much noise in a regular build. # Use make W=1 to enable them (see scripts/Makefile.extrawarn) -KBUILD_CFLAGS += $(call cc-disable-warning, unused-but-set-variable) +KBUILD_CFLAGS += -Wno-unused-but-set-variable endif KBUILD_CFLAGS += $(call cc-disable-warning, unused-const-variable) |