aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/Makefile.extrawarn
diff options
context:
space:
mode:
authorMasahiro Yamada <masahiroy@kernel.org>2020-03-10 19:12:50 +0900
committerMasahiro Yamada <masahiroy@kernel.org>2020-03-12 07:43:03 +0900
commit3a7c733165a4799fa1beb262fe244bfbcdd1c163 (patch)
tree9998af16dd2464632fbc5a37339a11e971bc36de /scripts/Makefile.extrawarn
parentkconfig: introduce m32-flag and m64-flag (diff)
downloadlinux-dev-3a7c733165a4799fa1beb262fe244bfbcdd1c163.tar.xz
linux-dev-3a7c733165a4799fa1beb262fe244bfbcdd1c163.zip
int128: fix __uint128_t compiler test in Kconfig
The support for __uint128_t is dependent on the target bit size. GCC that defaults to the 32-bit can still build the 64-bit kernel with -m64 flag passed. However, $(cc-option,-D__SIZEOF_INT128__=0) is evaluated against the default machine bit, which may not match to the kernel it is building. Theoretically, this could be evaluated separately for 64BIT/32BIT. config CC_HAS_INT128 bool default !$(cc-option,$(m64-flag) -D__SIZEOF_INT128__=0) if 64BIT default !$(cc-option,$(m32-flag) -D__SIZEOF_INT128__=0) I simplified it more because the 32-bit compiler is unlikely to support __uint128_t. Fixes: c12d3362a74b ("int128: move __uint128_t compiler test to Kconfig") Reported-by: George Spelvin <lkml@sdf.org> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Tested-by: George Spelvin <lkml@sdf.org>
Diffstat (limited to 'scripts/Makefile.extrawarn')
0 files changed, 0 insertions, 0 deletions