mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-20 11:33:24 +02:00
2ca6c65ad5
passes too many time. I think this is actually the issue that someone raised with me at the developer's meeting and in an email, but that we never really got to the bottom of. Having all the testing utilities made it much easier to dig down and uncover the core issue. When a pass manager is running many passes over a single function, we need it to invalidate the analyses between each run so that they can be re-computed as needed. We also need to track the intersection of preserved higher-level analyses across all the passes that we run (for example, if there is one module analysis which all the function analyses preserve, we want to track that and propagate it). Unfortunately, this interacted poorly with any enclosing pass adaptor between two IR units. It would see the intersection of preserved analyses, and need to invalidate any other analyses, but some of the un-preserved analyses might have already been invalidated *and recomputed*! We would fail to propagate the fact that the analysis had already been invalidated. The solution to this struck me as really strange at first, but the more I thought about it, the more natural it seemed. After a nice discussion with Duncan about it on IRC, it seemed even nicer. The idea is that invalidating an analysis *causes* it to be preserved! Preserving the lack of result is trivial. If it is recomputed, great. Until something *else* invalidates it again, we're good. The consequence of this is that the invalidate methods on the analysis manager which operate over many passes now consume their PreservedAnalyses object, update it to "preserve" every analysis pass to which it delivers an invalidation (regardless of whether the pass chooses to be removed, or handles the invalidation itself by updating itself). Then we return this augmented set from the invalidate routine, letting the pass manager take the result and use the intersection of *that* across each pass run to compute the final preserved set. This accounts for all the places where the early invalidation of an analysis has already "preserved" it for a future run. I've beefed up the testing and adjusted the assertions to show that we no longer repeatedly invalidate or compute the analyses across nested pass managers. llvm-svn: 225333 |
||
|---|---|---|
| .. | ||
| AliasAnalysis.h | ||
| AliasSetTracker.h | ||
| AssumptionCache.h | ||
| BlockFrequencyInfo.h | ||
| BlockFrequencyInfoImpl.h | ||
| BranchProbabilityInfo.h | ||
| CallGraph.h | ||
| CallGraphSCCPass.h | ||
| CallPrinter.h | ||
| CaptureTracking.h | ||
| CFG.h | ||
| CFGPrinter.h | ||
| CGSCCPassManager.h | ||
| CodeMetrics.h | ||
| ConstantFolding.h | ||
| ConstantsScanner.h | ||
| DependenceAnalysis.h | ||
| DominanceFrontier.h | ||
| DominanceFrontierImpl.h | ||
| DomPrinter.h | ||
| DOTGraphTraitsPass.h | ||
| FunctionTargetTransformInfo.h | ||
| InlineCost.h | ||
| InstructionSimplify.h | ||
| Interval.h | ||
| IntervalIterator.h | ||
| IntervalPartition.h | ||
| IVUsers.h | ||
| JumpInstrTableInfo.h | ||
| LazyCallGraph.h | ||
| LazyValueInfo.h | ||
| LibCallAliasAnalysis.h | ||
| LibCallSemantics.h | ||
| Lint.h | ||
| Loads.h | ||
| LoopInfo.h | ||
| LoopInfoImpl.h | ||
| LoopIterator.h | ||
| LoopPass.h | ||
| MemoryBuiltins.h | ||
| MemoryDependenceAnalysis.h | ||
| Passes.h | ||
| PHITransAddr.h | ||
| PostDominators.h | ||
| PtrUseVisitor.h | ||
| RegionInfo.h | ||
| RegionInfoImpl.h | ||
| RegionIterator.h | ||
| RegionPass.h | ||
| RegionPrinter.h | ||
| ScalarEvolution.h | ||
| ScalarEvolutionExpander.h | ||
| ScalarEvolutionExpressions.h | ||
| ScalarEvolutionNormalization.h | ||
| SparsePropagation.h | ||
| TargetFolder.h | ||
| TargetTransformInfo.h | ||
| Trace.h | ||
| ValueTracking.h | ||