Revision f3604272e140cd17aae6091dbeece9258315e027 authored by Steven Johnson on 06 October 2022, 17:21:28 UTC, committed by GitHub on 06 October 2022, 17:21:28 UTC
Running JIT code under MSAN is (still) not officially supported, as it can (and does) give false positives; that said, this PR reduces the false positives in some cases. Specifically: (1) if we are building a JIT shared runtime (ie, we are jitting), and we are compiling with MSAN enabled (detected via preprocessor), we should always use the real MSAN stubs, even if the Target::MSan feature has been cleared (because JITModule::make_module() clears it). (2) Target::get_jit_from_environment() should add any detected sanitizer bits to the target sniffed from HL_JIT_TARGET
1 parent e3bbafd
| File | Mode | Size |
|---|---|---|
| CMakeLists.txt | -rw-r--r-- | 290 bytes |
| Halide-VS2017.natvis | -rw-r--r-- | 2.2 KB |
| Halide.natvis | -rw-r--r-- | 1.4 KB |
| HalideTraceDump.cpp | -rw-r--r-- | 11.6 KB |
| HalideTraceUtils.cpp | -rw-r--r-- | 1.4 KB |
| HalideTraceUtils.h | -rw-r--r-- | 2.7 KB |
| HalideTraceViz.cpp | -rw-r--r-- | 55.9 KB |
| inconsolata.h | -rw-r--r-- | 228.4 KB |
Computing file changes ...
