forked from OSchip/llvm-project
b1cd393f9e
Currently, FunctionModRefBehavior tracks whether the function reads or writes memory (ModRefInfo) and which locations it can access (argmem, inaccessiblemem and other). This patch changes it to track ModRef information per-location instead. To give two examples of why this is useful: * D117095 highlights a weakness of ModRef modelling in the presence of operand bundles. For a memcpy call with deopt operand bundle, we want to say that it can read any memory, but only write argument memory. This would allow them to be treated like any other calls. However, we currently can't express this and have to say that it can read or write any memory. * D127383 would ideally be modelled as a separate threadid location, where threadid Refs outside pre-split coroutines can be ignored (like other accesses to constant memory). The current representation does not allow modelling this precisely. The patch as implemented is intended to be NFC, but there are some obvious opportunities for improvements and simplification. To fully capitalize on this we would also want to change the way we represent memory attributes on functions, but that's a larger change, and I think it makes sense to separate out the FunctionModRefBehavior refactoring. Differential Revision: https://reviews.llvm.org/D130896 |
||
|---|---|---|
| .. | ||
| DependenceInfo.cpp | ||
| PolyhedralInfo.cpp | ||
| PruneUnprofitable.cpp | ||
| ScopBuilder.cpp | ||
| ScopDetection.cpp | ||
| ScopDetectionDiagnostic.cpp | ||
| ScopGraphPrinter.cpp | ||
| ScopInfo.cpp | ||
| ScopPass.cpp | ||