OSDN Git Service

kbuild: use -S instead of -E for precise cc-option test in Kconfig
authorMasahiro Yamada <masahiroy@kernel.org>
Fri, 17 Jan 2020 17:14:35 +0000 (02:14 +0900)
committerMasahiro Yamada <masahiroy@kernel.org>
Wed, 22 Jan 2020 02:04:28 +0000 (11:04 +0900)
commit3bed1b7b9d79ca40e41e3af130931a3225e951a3
tree4b73fc5ee26959c9fce6745f06baaeba594dcc3f
parent1a7f0a34ea7d05d1ffcd32c9b1b4e07ac0687538
kbuild: use -S instead of -E for precise cc-option test in Kconfig

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>
scripts/Kconfig.include