From 77980cd8b25d6bc97f4f019fb2491acb27e5fc76 Mon Sep 17 00:00:00 2001 From: Lukáš Zaoral Date: Sat, 22 Jan 2022 21:27:43 +0100 Subject: CI: drop `-fsanitize=integer` from UBSAN flags When combined with `-fsanitize=undefined`, this flag only enables extra checks for unsigned integer overflow and (possibly bug-prone) implicit conversions between integer types. It was generating way too much noise (both for KLEE and its dependencies) and the reported problems do not lead to an undefined behaviour according to the C++ standard. --- scripts/build/v-sanitizer.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'scripts') diff --git a/scripts/build/v-sanitizer.inc b/scripts/build/v-sanitizer.inc index 1224beb0..e92d6f69 100644 --- a/scripts/build/v-sanitizer.inc +++ b/scripts/build/v-sanitizer.inc @@ -70,7 +70,7 @@ setup_variables_sanitizer() { # Undefined Behaviour Sanitizer if [ "${sanitizer}" == "undefined" ]; then echo "Using UBSan" - flags=("-fsanitize=undefined" "-fno-omit-frame-pointer" "-g" "-fsanitize=integer") + flags=("-fsanitize=undefined" "-fno-omit-frame-pointer" "-g") SANITIZER_CXX_FLAGS+=("${flags[@]}") SANITIZER_C_FLAGS+=("${flags[@]}") SANITIZER_LD_FLAGS+=("${flags[@]}") -- cgit 1.4.1