summaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2019-12-11 14:39:28 +0100
committerKees Cook <keescook@chromium.org>2020-01-02 13:30:14 -0800
commita5b0dc5a46c221725c43bd9b01570239a4cd78b1 (patch)
tree98c087571f7d028ce354ca7a4323ccb825c21262 /block
parentfd6988496e79a6a4bdb514a4655d2920209eb85d (diff)
downloadlinux-stable-a5b0dc5a46c221725c43bd9b01570239a4cd78b1.tar.gz
linux-stable-a5b0dc5a46c221725c43bd9b01570239a4cd78b1.tar.bz2
linux-stable-a5b0dc5a46c221725c43bd9b01570239a4cd78b1.zip
gcc-plugins: make it possible to disable CONFIG_GCC_PLUGINS again
I noticed that randconfig builds with gcc no longer produce a lot of ccache hits, unlike with clang, and traced this back to plugins now being enabled unconditionally if they are supported. I am now working around this by adding export CCACHE_COMPILERCHECK=/usr/bin/size -A %compiler% to my top-level Makefile. This changes the heuristic that ccache uses to determine whether the plugins are the same after a 'make clean'. However, it also seems that being able to just turn off the plugins is generally useful, at least for build testing it adds noticeable overhead but does not find a lot of bugs additional bugs, and may be easier for ccache users than my workaround. Fixes: 9f671e58159a ("security: Create "kernel hardening" config area") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Reviewed-by: Masahiro Yamada <masahiroy@kernel.org> Link: https://lore.kernel.org/r/20191211133951.401933-1-arnd@arndb.de Cc: stable@vger.kernel.org Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions