forked from OSchip/llvm-project
530e074faa
The motivation here is to make it available in the base class whether a fact is managed or not. That would have meant three flags on the base class, so I had a look whether we really have 8 possible combinations. It turns out we don't: asserted and declared are obviously mutually exclusive. Managed facts are only created when we acquire a capability through a scoped capability. Adopting an asserted or declared lock will not (in fact can not, because Facts are immutable) make them managed. We probably don't want to allow adopting an asserted lock (because then the function should probably have a release attribute, and then the assertion is pointless), but we might at some point decide to replace a declared fact on adoption. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D100801 |
||
|---|---|---|
| .. | ||
| APINotes | ||
| ARCMigrate | ||
| AST | ||
| ASTMatchers | ||
| Analysis | ||
| Basic | ||
| CodeGen | ||
| CrossTU | ||
| DirectoryWatcher | ||
| Driver | ||
| Edit | ||
| Format | ||
| Frontend | ||
| FrontendTool | ||
| Headers | ||
| Index | ||
| IndexSerialization | ||
| Lex | ||
| Parse | ||
| Rewrite | ||
| Sema | ||
| Serialization | ||
| StaticAnalyzer | ||
| Testing | ||
| Tooling | ||
| CMakeLists.txt | ||