summaryrefslogtreecommitdiffstats
path: root/llvm/test/Instrumentation/ThreadSanitizer/do-not-instrument-memory-access.ll
Commit message (Collapse)AuthorAgeFilesLines
* [tsan] Don't instrument __llvm_gcov_global_state_pred or __llvm_gcda*Vedant Kumar2016-07-191-0/+13
| | | | | | | | | | r274801 did not go far enough to allow gcov+tsan to cooperate. With this commit it's possible to run the following code without false positives: std::thread T1(fib), T2(fib); T1.join(); T2.join(); llvm-svn: 276015
* [tsan] Try harder to not instrument gcov countersVedant Kumar2016-07-071-0/+5
| | | | | | | | GCOVProfiler::emitProfileArcs() can create many variables with names starting with "__llvm_gcov_ctr", so llvm appends a numeric suffix to most of them. Teach tsan about this. llvm-svn: 274801
* [tsan] Do not instrument accesses to the gcov counters arrayVedant Kumar2016-06-201-0/+8
| | | | | | | | There is a known intended race here. This is a follow-up to r264805, which disabled tsan instrumentation for updates to instrprof counters. For more background on this please see the discussion in D18164. llvm-svn: 273202
* [tsan] Do not instrument reads/writes to instruction profile counters.Anna Zaks2016-03-291-0/+33
We have known races on profile counters, which can be reproduced by enabling -fsanitize=thread and -fprofile-instr-generate simultaneously on a multi-threaded program. This patch avoids reporting those races by not instrumenting the reads and writes coming from the instruction profiler. llvm-svn: 264805
OpenPOWER on IntegriCloud