forked from OSchip/llvm-project
f081ec7609
Summary: I made a mistake in handling transitive invalidation of analysis results. I've updated the list of preserved analyses as well as the correct result dependences. The Invalidator passed through the invalidate() path can be used to transitively invalidate analyses. It frequently happens that analysis results depend on other analyses, and thus store references to their results. When the dependee now gets invalidated, the depender needs to be invalidated as well. This is the purpose of the Invalidator object, which can be used to check whether some dependee analysis is in the process of being invalidated. I originally was checking the wrong dependee analyses, which is an actual error, you can only check analysis results that are in the cache (which they are if you've captured their reference). The invalidation I'm handling inside the proxy deals with the standard analyses the proxy passes into the Scop pipeline, since I'm capturing their reference. This checking allows us to actually preserve a couple of results outside of the proxy, since the Scop pipeline shouldn't break those, or otherwise should update them accordingly. Reviewers: grosser, Meinersbur, bollu Reviewed By: grosser Subscribers: pollydev, llvm-commits Differential Revision: https://reviews.llvm.org/D36216 llvm-svn: 309811 |
||
|---|---|---|
| .. | ||
| DependenceInfo.cpp | ||
| PolyhedralInfo.cpp | ||
| PruneUnprofitable.cpp | ||
| ScopBuilder.cpp | ||
| ScopDetection.cpp | ||
| ScopDetectionDiagnostic.cpp | ||
| ScopGraphPrinter.cpp | ||
| ScopInfo.cpp | ||
| ScopPass.cpp | ||