-
Notifications
You must be signed in to change notification settings - Fork 12.2k
/
check-for-sanitizer-feature.cpp
66 lines (58 loc) · 2.84 KB
/
check-for-sanitizer-feature.cpp
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
// RUN: rm -rf %t.1 %t.2
// RUN: mkdir %t.1 %t.2
// Build and use an ASan-enabled module.
// RUN: %clang_cc1 -fsanitize=address -fmodules -fmodules-cache-path=%t.1 \
// RUN: -fmodule-map-file=%S/Inputs/check-for-sanitizer-feature/map \
// RUN: -I %S/Inputs/check-for-sanitizer-feature -verify %s
// RUN: ls %t.1 | count 2
// Force a module rebuild by disabling ASan.
// RUN: %clang_cc1 -fmodules -fmodules-cache-path=%t.1 \
// RUN: -fmodule-map-file=%S/Inputs/check-for-sanitizer-feature/map \
// RUN: -I %S/Inputs/check-for-sanitizer-feature -verify %s
// RUN: ls %t.1 | count 3
// Enable ASan again: check that there is no import failure, and no rebuild.
// RUN: %clang_cc1 -fsanitize=address -fmodules -fmodules-cache-path=%t.1 \
// RUN: -fmodule-map-file=%S/Inputs/check-for-sanitizer-feature/map \
// RUN: -I %S/Inputs/check-for-sanitizer-feature -verify %s
// RUN: ls %t.1 | count 3
// Some sanitizers can not affect AST generation when enabled. Check that
// module rebuilds don't occur when these sanitizers are enabled.
//
// First, build without any sanitization.
// RUN: %clang_cc1 -fmodules -fmodules-cache-path=%t.2 \
// RUN: -fmodule-map-file=%S/Inputs/check-for-sanitizer-feature/map \
// RUN: -I %S/Inputs/check-for-sanitizer-feature -verify %s
// RUN: ls %t.2 | count 2
//
// Next, build with sanitization, and check that a new module isn't built.
// RUN: %clang_cc1 -fsanitize=cfi-vcall,float-divide-by-zero,unsigned-integer-overflow,nullability-arg,null -fmodules \
// RUN: -fmodules-cache-path=%t.2 \
// RUN: -fmodule-map-file=%S/Inputs/check-for-sanitizer-feature/map \
// RUN: -I %S/Inputs/check-for-sanitizer-feature -verify %s
// RUN: ls %t.2 | count 2
// Finally, test that including enabled sanitizers in the module hash isn't
// required to ensure correctness of module imports.
//
// Emit a PCH with ASan enabled.
// RUN: %clang_cc1 -x c -fsanitize=address %S/Inputs/check-for-sanitizer-feature/check.h -emit-pch -o %t.asan_pch
//
// Import the PCH without ASan enabled (we expect an error).
// RUN: not %clang_cc1 -x c -include-pch %t.asan_pch %s -verify 2>&1 | FileCheck %s --check-prefix=PCH_MISMATCH
// PCH_MISMATCH: AST file was compiled with the target feature '-fsanitize=address' but the current translation unit is not
//
// Emit a PCH with UBSan enabled.
// RUN: %clang_cc1 -x c -fsanitize=null %S/Inputs/check-for-sanitizer-feature/check.h -emit-pch -o %t.ubsan_pch
//
// Import the PCH without UBSan enabled (should work just fine).
// RUN: %clang_cc1 -x c -include-pch %t.ubsan_pch %s -I %S/Inputs/check-for-sanitizer-feature -verify
#include "check.h"
#if __has_feature(address_sanitizer)
#if HAS_ASAN != 1
#error Module doesn't have the address_sanitizer feature, but main program does.
#endif
#else
#if HAS_ASAN != 0
#error Module has the address_sanitizer feature, but main program doesn't.
#endif
#endif
// expected-no-diagnostics