aboutsummaryrefslogtreecommitdiff
path: root/scripts/kconfig
diff options
context:
space:
mode:
authorGravatar Masahiro Yamada <masahiroy@kernel.org> 2022-09-16 15:29:53 +0900
committerGravatar Masahiro Yamada <masahiroy@kernel.org> 2022-09-29 04:40:15 +0900
commitf3304ecd7f060db1d4197fbdce5a503259f770d3 (patch)
tree3e4cbf7e79aa70b17fe39ae202d00859d14be4d9 /scripts/kconfig
parentkbuild: use objtool-args-y to clean up objtool arguments (diff)
downloadlinux-f3304ecd7f060db1d4197fbdce5a503259f770d3.tar.gz
linux-f3304ecd7f060db1d4197fbdce5a503259f770d3.tar.bz2
linux-f3304ecd7f060db1d4197fbdce5a503259f770d3.zip
linux/export: use inline assembler to populate symbol CRCs
Since commit 7b4537199a4a ("kbuild: link symbol CRCs at final link, removing CONFIG_MODULE_REL_CRCS"), the module versioning on the (non-upstreamed-yet) kvx Linux port is broken due to unexpected padding for __crc_* symbols. The kvx GCC adds padding so u32 gets 8-byte alignment instead of 4. I do not know if this happens for upstream architectures in general, but any compiler has the freedom to insert padding for faster access. Use the inline assembler to directly specify the wanted data layout. This is how we previously did before the breakage. Link: https://lore.kernel.org/lkml/20220817161438.32039-1-ysionneau@kalray.eu/ Link: https://lore.kernel.org/linux-kbuild/31ce5305-a76b-13d7-ea55-afca82c46cf2@kalray.eu/ Fixes: 7b4537199a4a ("kbuild: link symbol CRCs at final link, removing CONFIG_MODULE_REL_CRCS") Reported-by: Yann Sionneau <ysionneau@kalray.eu> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Tested-by: Yann Sionneau <ysionneau@kalray.eu>
Diffstat (limited to 'scripts/kconfig')
0 files changed, 0 insertions, 0 deletions