aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/DebugInfo/PDB/Native/ModuleDebugStream.cpp
diff options
context:
space:
mode:
authorDmitry Vyukov <dvyukov@google.com>2017-05-01 10:01:13 +0000
committerDmitry Vyukov <dvyukov@google.com>2017-05-01 10:01:13 +0000
commit5fa9175e24eaafadab71361dfe4f0f51b96ba4e9 (patch)
tree698608e19caf3b5638a5a55d4c00c877c59a17c4 /llvm/lib/DebugInfo/PDB/Native/ModuleDebugStream.cpp
parent59e7fe3da8092e7dfb13376b959418bb507eaf87 (diff)
downloadllvm-5fa9175e24eaafadab71361dfe4f0f51b96ba4e9.zip
llvm-5fa9175e24eaafadab71361dfe4f0f51b96ba4e9.tar.gz
llvm-5fa9175e24eaafadab71361dfe4f0f51b96ba4e9.tar.bz2
tsan: support linker init flag in __tsan_mutex_destroy
For a linker init mutex with lazy flag setup (no __tsan_mutex_create call), it is possible that no lock/unlock happened before the destroy call. Then when destroy runs we still don't know that it is a linker init mutex and will emulate a memory write. This in turn can lead to false positives as the mutex is in fact linker initialized. Support linker init flag in destroy annotation to resolve this. llvm-svn: 301795
Diffstat (limited to 'llvm/lib/DebugInfo/PDB/Native/ModuleDebugStream.cpp')
0 files changed, 0 insertions, 0 deletions