search for: loopanalysismanag

...leAnalysisManagerLoopProxy for a loop pass to be > able to get to the ModuleAnalysisManager and PSI because it may not > always through (const) FunctionAnalysisManager, > unless ModuleAnalysisManagerFunctionProxy is already cached. > > Since FunctionAnalysisManager we can get from LoopAnalysisManager is a > const ref, we cannot call getResult on it and always get > ModuleAnalysisManager and PSI (see below.) This actually happens in my > experiment. > > SomeLoopPass::run(Loop &L, LoopAnalysisManager &LAM, …) { > auto &FAM = LAM.getResult<FunctionAnalysisMana...

...assAdaptor which is essentially the same as the FunctionToLoopPassAdaptor but operates only on LI.getTopLevelLoops(). We might also need a LNPMUpdater (LoopNestPassManagerUpdater) which disallows adding inner-loops back into the pipeline, and LoopNestPassManager will simply be PassManager<Loop, LoopAnalysisManager, LoopStandardAnalysisResult &, LNPMUpdater &>. One question I have is whether the IRUnit LoopNestPass operates on should be Loop or LoopNest, since I'm not quite sure about the usage of LoopNest and why it should be constructed with a ScalarEvolution. Also, it is stated that &quo...

Overall seems fine to me. On 3/11/19 8:12 PM, Hiroshi Yamauchi wrote: > Here's a revised approach based on the discussion: > > - Cache PSI right after the profile summary in the IR is written in > the pass pipeline. This would avoid the need to insert > RequireAnalysisPass for PSI before each non-module pass that needs it. > PSI can be technically invalidated but unlikely

...quot;Create > LoopNestPass" > Date: Sat, Jul 18, 2020 3:32 PM > > Hi Ta-Wei, > > > We might also need a LNPMUpdater (LoopNestPassManagerUpdater) which > disallows adding inner-loops back into the pipeline, and > LoopNestPassManager will simply be PassManager<Loop, LoopAnalysisManager, > LoopStandardAnalysisResult &, LNPMUpdater &>. > > LNPMUpdater should have some functionalities of LPMUpdater, e.g. adding > sibling loop nest, revisit the current loop nest, etc. > > > One question I have is whether the IRUnit LoopNestPass operates on > shoul...

Hi Philip, Thanks for the response. Under llvm-5.0.2 and llvm-6.0.1 in Debug mode, the crash hit at the same assertion: /usr/local/include/llvm/IR/PassManager.h:689: typename PassT::Result& llvm::AnalysisManager<IRUnitT, ExtraArgTs>::getResult(IRUnitT&, ExtraArgTs ...) [with PassT = llvm::InnerAnalysisManagerProxy<llvm::AnalysisManager<llvm::Loop,

Hi, I'm a college student who is quite new to the community and is interested in contributing to the LLVM project. Although I haven't applied to GSoC, I notice that the project "Create LoopNestPass" seems to be unassigned. So I'm curious whether anyone is currently working on it, and if not, is it possible for me to work on it as a side-project? I've been programming in