diff options
author | Nathan Chancellor <nathan@kernel.org> | 2023-01-11 20:05:05 -0700 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2023-01-26 12:42:40 +0900 |
commit | 05e05bfc92d196669a3d087fc34d3998b6ddb758 (patch) | |
tree | e20642880e48ca05cbc411e23eb780e494aa90ee /arch/s390 | |
parent | f0a42fbab447ed9f55bbd99751183e71f3a1f6ec (diff) | |
download | linux-stable-05e05bfc92d196669a3d087fc34d3998b6ddb758.tar.gz linux-stable-05e05bfc92d196669a3d087fc34d3998b6ddb758.tar.bz2 linux-stable-05e05bfc92d196669a3d087fc34d3998b6ddb758.zip |
powerpc/vdso: Remove an unsupported flag from vgettimeofday-32.o with clang
When clang's -Qunused-arguments is dropped from KBUILD_CPPFLAGS, it
warns:
clang-16: error: argument unused during compilation: '-fno-stack-clash-protection' [-Werror,-Wunused-command-line-argument]
This warning happens because vgettimeofday-32.c gets its base CFLAGS
from the main kernel, which may contain flags that are only supported on
a 64-bit target but not a 32-bit one, which is the case here.
-fstack-clash-protection and its negation are only suppported by the
64-bit powerpc target but that flag is included in an invocation for a
32-bit powerpc target, so clang points out that while the flag is one
that it recognizes, it is not actually used by this compiler job.
To eliminate the warning, remove -fno-stack-clash-protection from
vgettimeofday-32.c's CFLAGS when using clang, as has been done for other
flags previously.
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
Tested-by: Anders Roxell <anders.roxell@linaro.org>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'arch/s390')
0 files changed, 0 insertions, 0 deletions