summaryrefslogtreecommitdiff
path: root/scripts/kconfig
diff options
context:
space:
mode:
authorMasahiro Yamada <masahiroy@kernel.org>2020-01-17 20:14:35 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-02-24 10:34:50 +0300
commit4feefb5cd5859dfcd9e4ce1e6dd7265052c2da04 (patch)
treebf41005dd5bb0e93cbd4093b7d1b7372da128e7b /scripts/kconfig
parentafdf4de910986e50567c92b9e4ff901606013978 (diff)
downloadlinux-4feefb5cd5859dfcd9e4ce1e6dd7265052c2da04.tar.xz
kbuild: use -S instead of -E for precise cc-option test in Kconfig
[ Upstream commit 3bed1b7b9d79ca40e41e3af130931a3225e951a3 ] Currently, -E (stop after the preprocessing stage) is used to check whether the given compiler flag is supported. While it is faster than -S (or -c), it can be false-positive. You need to run the compilation proper to check the flag more precisely. For example, -E and -S disagree about the support of "--param asan-instrument-allocas=1". $ gcc -Werror --param asan-instrument-allocas=1 -E -x c /dev/null -o /dev/null $ echo $? 0 $ gcc -Werror --param asan-instrument-allocas=1 -S -x c /dev/null -o /dev/null cc1: error: invalid --param name ‘asan-instrument-allocas’; did you mean ‘asan-instrument-writes’? $ echo $? 1 Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/kconfig')
0 files changed, 0 insertions, 0 deletions