forked from Minki/linux
c17eb4dca5
Declaring setjmp()/longjmp() as taking longs makes the signature
non-standard, and makes clang complain. In the past, this has been
worked around by adding -ffreestanding to the compile flags.
The implementation looks like it only ever propagates the value
(in longjmp) or sets it to 1 (in setjmp), and we only call longjmp
with integer parameters.
This allows removing -ffreestanding from the compilation flags.
Fixes: c9029ef9c9 ("powerpc: Avoid clang warnings around setjmp and longjmp")
Cc: stable@vger.kernel.org # v4.14+
Signed-off-by: Clement Courbet <courbet@google.com>
Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>
Tested-by: Nathan Chancellor <natechancellor@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20200330080400.124803-1-courbet@google.com
23 lines
450 B
Makefile
23 lines
450 B
Makefile
# SPDX-License-Identifier: GPL-2.0
|
|
#
|
|
# Makefile for the linux kernel.
|
|
#
|
|
|
|
obj-y += core.o crash.o core_$(BITS).o
|
|
|
|
obj-$(CONFIG_PPC32) += relocate_32.o
|
|
|
|
obj-$(CONFIG_KEXEC_FILE) += file_load.o elf_$(BITS).o
|
|
|
|
ifdef CONFIG_HAVE_IMA_KEXEC
|
|
ifdef CONFIG_IMA
|
|
obj-y += ima.o
|
|
endif
|
|
endif
|
|
|
|
|
|
# Disable GCOV, KCOV & sanitizers in odd or sensitive code
|
|
GCOV_PROFILE_core_$(BITS).o := n
|
|
KCOV_INSTRUMENT_core_$(BITS).o := n
|
|
UBSAN_SANITIZE_core_$(BITS).o := n
|