forked from luck/tmp_suning_uos_patched
kcsan: Re-add GCC as a supported compiler
GCC version 11 recently implemented all requirements to correctly support KCSAN: 1. Correct no_sanitize-attribute inlining behaviour: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=4089df8ef4a63126b0774c39b6638845244c20d2 2. --param=tsan-distinguish-volatile https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=ab2789ec507a94f1a75a6534bca51c7b39037ce0 3. --param=tsan-instrument-func-entry-exit https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=06712fc68dc9843d9af7c7ac10047f49d305ad76 Therefore, we can re-enable GCC for KCSAN, and document the new compiler requirements. Signed-off-by: Marco Elver <elver@google.com> Cc: Martin Liska <mliska@suse.cz> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
This commit is contained in:
parent
56b031f0ab
commit
e68dcd8eac
|
@ -8,7 +8,8 @@ approach to detect races. KCSAN's primary purpose is to detect `data races`_.
|
|||
Usage
|
||||
-----
|
||||
|
||||
KCSAN requires Clang version 11 or later.
|
||||
KCSAN is supported by both GCC and Clang. With GCC we require version 11 or
|
||||
later, and with Clang also require version 11 or later.
|
||||
|
||||
To enable KCSAN configure the kernel with::
|
||||
|
||||
|
|
|
@ -4,7 +4,8 @@ config HAVE_ARCH_KCSAN
|
|||
bool
|
||||
|
||||
config HAVE_KCSAN_COMPILER
|
||||
def_bool CC_IS_CLANG && $(cc-option,-fsanitize=thread -mllvm -tsan-distinguish-volatile=1)
|
||||
def_bool (CC_IS_CLANG && $(cc-option,-fsanitize=thread -mllvm -tsan-distinguish-volatile=1)) || \
|
||||
(CC_IS_GCC && $(cc-option,-fsanitize=thread --param tsan-distinguish-volatile=1))
|
||||
help
|
||||
For the list of compilers that support KCSAN, please see
|
||||
<file:Documentation/dev-tools/kcsan.rst>.
|
||||
|
|
|
@ -6,7 +6,7 @@ ifdef CONFIG_KCSAN
|
|||
ifdef CONFIG_CC_IS_CLANG
|
||||
cc-param = -mllvm -$(1)
|
||||
else
|
||||
cc-param = --param -$(1)
|
||||
cc-param = --param $(1)
|
||||
endif
|
||||
|
||||
# Keep most options here optional, to allow enabling more compilers if absence
|
||||
|
|
Loading…
Reference in New Issue
Block a user