Dmitry Vyukov 31e6082bb3 asan: optimization experiments ... The experiments can be used to evaluate potential optimizations that remove instrumentation (assess false negatives). Instead of completely removing some instrumentation, you set Exp to a non-zero value (mask of optimization experiments that want to remove instrumentation of this instruction). If Exp is non-zero, this pass will emit special calls into runtime (e.g. __asan_report_exp_load1 instead of __asan_report_load1). These calls make runtime terminate the program in a special way (with a different exit status). Then you run the new compiler on a buggy corpus, collect the special terminations (ideally, you don't see them at all -- no false negatives) and make the decision on the optimization. The exact reaction to experiments in runtime is not implemented in this patch. It will be defined and implemented in a subsequent patch. http://reviews.llvm.org/D8198 llvm-svn: 232502		2015-03-17 16:59:19 +00:00
..
AddressSanitizer	asan: optimization experiments	2015-03-17 16:59:19 +00:00
BoundsChecking	Add a bunch of CHECK missing colons in tests. NFC.	2015-03-14 01:43:57 +00:00
DataFlowSanitizer	DebugInfo: Move new hierarchy into place	2015-03-03 17:24:31 +00:00
InstrProfiling	[opaque pointer type] Add textual IR support for explicit type parameter to gep operator	2015-03-13 18:20:45 +00:00
MemorySanitizer	DebugInfo: Move new hierarchy into place	2015-03-03 17:24:31 +00:00
SanitizerCoverage	[sanitizer] fix instrumentation with -mllvm -sanitizer-coverage-block-threshold=0 to actually do something useful.	2015-03-10 01:58:27 +00:00
ThreadSanitizer	[opaque pointer type] Add textual IR support for explicit type parameter to gep operator	2015-03-13 18:20:45 +00:00