aboutsummaryrefslogtreecommitdiffstats
path: root/arch/um
diff options
context:
space:
mode:
authorNathan Chancellor <nathan@kernel.org>2022-03-30 16:45:27 -0700
committerMasahiro Yamada <masahiroy@kernel.org>2022-04-02 00:05:28 +0900
commitcf300b83c793c25c6b485fdaf7a4447d8ea4c655 (patch)
treef094949a5a81b095c6073c630450f1a5e33adc12 /arch/um
parentkbuild: fix empty ${PYTHON} in scripts/link-vmlinux.sh (diff)
downloadlinux-dev-cf300b83c793c25c6b485fdaf7a4447d8ea4c655.tar.xz
linux-dev-cf300b83c793c25c6b485fdaf7a4447d8ea4c655.zip
kbuild: Remove '-mno-global-merge'
This flag is specific to clang, where it is only used by the 32-bit and 64-bit ARM backends. In certain situations, the presence of this flag will cause a warning, as shown by commit 6580c5c18fb3 ("um: clang: Strip out -mno-global-merge from USER_CFLAGS"). Since commit 61163efae020 ("kbuild: LLVMLinux: Add Kbuild support for building kernel with Clang") that added this flag back in 2014, there have been quite a few changes to the GlobalMerge pass in LLVM. Building several different ARCH=arm and ARCH=arm64 configurations with LLVM 11 (minimum) and 15 (current main version) with this flag removed (i.e., with the default of '-mglobal-merge') reveals no modpost warnings, so it is likely that the issue noted in the comment is no longer relevant due to changes in LLVM or modpost, meaning this flag can be removed. If any new warnings show up that are a result of the removal of this flag, it can be added back under arch/arm{,64}/Makefile to avoid warnings on other architectures. Signed-off-by: Nathan Chancellor <nathan@kernel.org> Tested-by: David Gow <davidgow@google.com> Reviewed-by: Kees Cook <keescook@chromium.org> Tested-by: Sedat Dilek <sedat.dilek@gmail.com> Reviewed-by: Sedat Dilek <sedat.dilek@gmail.com> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'arch/um')
0 files changed, 0 insertions, 0 deletions