aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorAlex Shlyapnikov <alekseys@google.com>2017-05-25 15:07:07 +0000
committerAlex Shlyapnikov <alekseys@google.com>2017-05-25 15:07:07 +0000
commit3ea9499e7578616c2d48aec3b5ffaf9fef5a7e90 (patch)
treeabc6a6165e053b28c1f80e775ede565bf12a6357 /clang/lib/Frontend/CompilerInvocation.cpp
parentfc50f62caafd35b3dd4297d7af109fb7e6c00675 (diff)
downloadllvm-3ea9499e7578616c2d48aec3b5ffaf9fef5a7e90.zip
llvm-3ea9499e7578616c2d48aec3b5ffaf9fef5a7e90.tar.gz
llvm-3ea9499e7578616c2d48aec3b5ffaf9fef5a7e90.tar.bz2
[sanitizer] Pair atomic acquire with release in BlockingMutex::Unlock
Summary: Dmitry, seeking your expertise. I believe, the proper way to implement Lock/Unlock here would be to use acquire/release semantics. Am I missing something? Reviewers: dvyukov Subscribers: llvm-commits, kubamracek Differential Revision: https://reviews.llvm.org/D33521 llvm-svn: 303869
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions