projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: fc50f62) | patch
[sanitizer] Pair atomic acquire with release in BlockingMutex::Unlock
authorAlex Shlyapnikov <alekseys@google.com>
Thu, 25 May 2017 15:07:07 +0000 (15:07 +0000)
committerAlex Shlyapnikov <alekseys@google.com>
Thu, 25 May 2017 15:07:07 +0000 (15:07 +0000)
commit3ea9499e7578616c2d48aec3b5ffaf9fef5a7e90
treeabc6a6165e053b28c1f80e775ede565bf12a6357tree | snapshot
parentfc50f62caafd35b3dd4297d7af109fb7e6c00675commit | diff
[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
compiler-rt/lib/sanitizer_common/sanitizer_linux.cc diff | blob | history
Domain: System / Toolchain;