diff options
| author | Aaron Puchert <aaron.puchert@sap.com> | 2022-04-29 22:11:20 +0200 |
|---|---|---|
| committer | Aaron Puchert <aaron.puchert@sap.com> | 2022-04-29 22:30:33 +0200 |
| commit | d65c922450d1fdf0f44f4a10a8f33b11c6c01bf5 (patch) | |
| tree | b63ad0a60b891cf066e53d31503b8ad19c6aad18 /clang/lib/Analysis/ThreadSafetyCommon.cpp | |
| parent | dd1790cd05ae124e9e5d57dfe9279ff54f34b488 (diff) | |
| download | llvm-d65c922450d1fdf0f44f4a10a8f33b11c6c01bf5.zip llvm-d65c922450d1fdf0f44f4a10a8f33b11c6c01bf5.tar.gz llvm-d65c922450d1fdf0f44f4a10a8f33b11c6c01bf5.tar.bz2 | |
Thread safety analysis: Store CapabilityExprs in ScopedLockableFactEntry (NFC)
For now this doesn't make a whole lot of sense, but it will allow us to
store the capability kind in a CapabilityExpr and make sure it doesn't
get lost. The capabilities managed by a scoped lockable can of course be
of different kind, so we'll need to store that per entry.
Reviewed By: aaron.ballman
Differential Revision: https://reviews.llvm.org/D124128
Diffstat (limited to 'clang/lib/Analysis/ThreadSafetyCommon.cpp')
0 files changed, 0 insertions, 0 deletions