mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-12-15 04:30:12 +00:00
6f409cbc05
manager to support the actual uses of it. =] When I ported instcombine to the new pass manager I discover that it didn't work because TLI wasn't available in the right places. This is a somewhat surprising and/or subtle aspect of the new pass manager design that came up before but I think is useful to be reminded of: While the new pass manager *allows* a function pass to query a module analysis, it requires that the module analysis is already run and cached prior to the function pass manager starting up, possibly with a 'require<foo>' style utility in the pass pipeline. This is an intentional hurdle because using a module analysis from a function pass *requires* that the module analysis is run prior to entering the function pass manager. Otherwise the other functions in the module could be in who-knows-what state, etc. A somewhat surprising consequence of this design decision (at least to me) is that you have to design a function pass that leverages a module analysis to do so as an optional feature. Even if that means your function pass does no work in the absence of the module analysis, you have to handle that possibility and remain conservatively correct. This is a natural consequence of things being able to invalidate the module analysis and us being unable to re-run it. And it's a generally good thing because it lets us reorder passes arbitrarily without breaking correctness, etc. This ends up causing problems in one case. What if we have a module analysis that is *definitionally* impossible to invalidate. In the places this might come up, the analysis is usually also definitionally trivial to run even while other transformation passes run on the module, regardless of the state of anything. And so, it follows that it is natural to have a hard requirement on such analyses from a function pass. It turns out, that TargetLibraryInfo is just such an analysis, and InstCombine has a hard requirement on it. The approach I've taken here is to produce an analysis that models this flexibility by making it both a module and a function analysis. This exposes the fact that it is in fact safe to compute at any point. We can even make it a valid CGSCC analysis at some point if that is useful. However, we don't want to have a copy of the actual target library info state for each function! This state is specific to the triple. The somewhat direct and blunt approach here is to turn TLI into a pimpl, with the state and mutators in the implementation class and the query routines primarily in the wrapper. Then the analysis can lazily construct and cache the implementations, keyed on the triple, and on-demand produce wrappers of them for each function. One minor annoyance is that we will end up with a wrapper for each function in the module. While this is a bit wasteful (one pointer per function) it seems tolerable. And it has the advantage of ensuring that we pay the absolute minimum synchronization cost to access this information should we end up with a nice parallel function pass manager in the future. We could look into trying to mark when analysis results are especially cheap to recompute and more eagerly GC-ing the cached results, or we could look at supporting a variant of analyses whose results are specifically *not* cached and expected to just be used and discarded by the consumer. Either way, these seem like incremental enhancements that should happen when we start profiling the memory and CPU usage of the new pass manager and not before. The other minor annoyance is that if we end up using the TLI in both a module pass and a function pass, those will be produced by two separate analyses, and thus will point to separate copies of the implementation state. While a minor issue, I dislike this and would like to find a way to cleanly allow a single analysis instance to be used across multiple IR unit managers. But I don't have a good solution to this today, and I don't want to hold up all of the work waiting to come up with one. This too seems like a reasonable thing to incrementally improve later. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@226981 91177308-0d34-0410-b5e6-96231b3b80d8 |
||
|---|---|---|
| .. | ||
| 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 | ||
| TargetLibraryInfo.h | ||
| TargetTransformInfo.h | ||
| Trace.h | ||
| ValueTracking.h | ||