diff options
| author | Marco Elver <elver@google.com> | 2022-03-17 14:56:29 +0100 |
|---|---|---|
| committer | Marco Elver <elver@google.com> | 2022-03-17 14:59:37 +0100 |
| commit | cbe1e67eade900fa73f29b88ab49fcb6fc29bbb0 (patch) | |
| tree | 76b917ce73f23e189238ba80ed0071e119893ea1 /llvm/lib/CodeGen/LiveDebugValues/InstrRefBasedImpl.cpp | |
| parent | 799643f7f0bebbc4e45767cfea5e8e227af7ef9c (diff) | |
| download | llvm-cbe1e67eade900fa73f29b88ab49fcb6fc29bbb0.zip llvm-cbe1e67eade900fa73f29b88ab49fcb6fc29bbb0.tar.gz llvm-cbe1e67eade900fa73f29b88ab49fcb6fc29bbb0.tar.bz2 | |
[Instruction] Introduce getAtomicSyncScopeID()
An analysis may just be interested in checking if an instruction is
atomic but system scoped or single-thread scoped, like ThreadSanitizer's
isAtomic(). Unfortunately Instruction::isAtomic() can only answer the
"atomic" part of the question, but to also check scope becomes rather
verbose.
To simplify and reduce redundancy, introduce a common helper
getAtomicSyncScopeID() which returns the scope of an atomic operation.
Start using it in ThreadSanitizer.
NFCI.
Reviewed By: dvyukov
Differential Revision: https://reviews.llvm.org/D121910
Diffstat (limited to 'llvm/lib/CodeGen/LiveDebugValues/InstrRefBasedImpl.cpp')
0 files changed, 0 insertions, 0 deletions