Home
last modified time | relevance | path

Searched refs:MSAN (Results 1 – 20 of 20) sorted by relevance

/external/flac/oss-fuzz/fuzzing/
Dmemory.hpp10 #ifndef MSAN
11 #define MSAN 0 macro
22 #if MSAN == 1
43 #if MSAN == 1 in memory_test_msan()
65 #if MSAN == 1 in memory_test()
/external/skia/site/docs/dev/testing/
Dxsan.md3 title: "MSAN, ASAN, & TSAN"
4 linkTitle: "MSAN, ASAN, & TSAN"
16 - MSAN works on Linux[1].
23 [1]To compile and run with MSAN, an MSAN-instrumented version of libc++ is needed.
46 Configure and Compile Skia with MSAN
62 sanitize = "MSAN"
Dfuzz.md9 reproduce when building with ASAN or MSAN; see
/external/skqp/site/dev/testing/
Dxsan.md1 MSAN, ASAN, & TSAN
11 - MSAN works on Linux[1].
18 [1]To compile and run with MSAN, an MSAN-instrumented version of libc++ is needed.
41 Configure and Compile Skia with MSAN
57 sanitize = "MSAN"
Dfuzz.md5 when building with ASAN or MSAN; see [those instructions for more details](./xsan).
/external/llvm-project/llvm/test/Instrumentation/MemorySanitizer/
Dstore-origin.ll3 ; RUN: "-check-prefixes=CHECK,CHECK-MSAN,CHECK-ORIGINS1" %s
4 …s-address=0 -msan-track-origins=1 -S | FileCheck -check-prefixes=CHECK,CHECK-MSAN,CHECK-ORIGINS1 %s
7 ; RUN: "-check-prefixes=CHECK,CHECK-MSAN,CHECK-ORIGINS2" %s
8 …s-address=0 -msan-track-origins=2 -S | FileCheck -check-prefixes=CHECK,CHECK-MSAN,CHECK-ORIGINS2 %s
65 ; CHECK-MSAN: load {{.*}} @__msan_param_tls
66 ; CHECK-MSAN: [[ORIGIN:%[0-9a-z]+]] = load {{.*}} @__msan_param_origin_tls
Dmsan_basic.ll252 ;; verify that MSAN handles these intrinsics properly once they have been
/external/zstd/tests/fuzz/
DREADME.md66 ### MSAN subsection
68 Fuzzing with `libFuzzer` and `MSAN` is as easy as:
77 the extra parameters only for MSAN.
/external/oss-fuzz/infra/base-images/base-builder/test_data/
Dculprit-commit.txt12 Test Plan: Local MSAN failures caused by uninstrumented `getrandom`
/external/skqp/third_party/freetype2/
DBUILD.gn9 is_official_build || !(is_android || sanitize == "MSAN")
/external/skia/third_party/freetype2/
DBUILD.gn9 (is_official_build || !(is_android || sanitize == "MSAN")) && !is_fuchsia
/external/rust/crates/quiche/deps/boringssl/src/
DCMakeLists.txt306 if(MSAN)
308 message(FATAL_ERROR "Cannot enable MSAN unless using Clang")
312 message(FATAL_ERROR "ASAN and MSAN are mutually exclusive")
383 if(NOT ASAN AND NOT MSAN)
550 if(ASAN OR MSAN OR TSAN)
/external/boringssl/src/
DCMakeLists.txt306 if(MSAN)
308 message(FATAL_ERROR "Cannot enable MSAN unless using Clang")
312 message(FATAL_ERROR "ASAN and MSAN are mutually exclusive")
383 if(NOT ASAN AND NOT MSAN)
552 if(ASAN OR MSAN OR TSAN)
/external/skia/tools/
Dvalgrind.supp286 #It seems bogus after investigation. MSAN/ASAN have no complaints. It's complaining about
/external/oss-fuzz/infra/base-images/base-builder/
DDockerfile94 # Needed to recompile rust std library for MSAN
/external/skqp/gn/
DBUILD.gn242 } else if (sanitize == "MSAN") {
/external/llvm/docs/
DLibFuzzer.rst102 - MemorySanitizer_ (MSAN) detects uninitialized reads: code whose behavior relies on memory
104 MSAN can not be combined with other sanirizers and should be used as a seprate build.
230 If running w/o ASAN/MSAN, you may use 'ulimit -v' instead.
/external/llvm-project/llvm/docs/
DLibFuzzer.rst79 also build with MemorySanitizer_ (MSAN), but support is experimental::
84 …lang -g -O1 -fsanitize=fuzzer,memory mytarget.c # Builds the fuzz target with MSAN
273 If running w/o ASAN/MSAN, you may use 'ulimit -v' instead.
/external/skia/gn/skia/
DBUILD.gn285 } else if (sanitize == "MSAN") {
/external/swiftshader/
DCMakeLists.txt172 option_if_not_defined(REACTOR_ENABLE_MEMORY_SANITIZER_INSTRUMENTATION "Include JIT in MSAN instrume…