search for: requiredpass

...able to schedule passes in > requested order. Pass manager is not able to find required pass at the same > level (module, function, loop etc..) or higher level compared current pass. Ok, that gives me some ideas. I didn't understand what "level" means. > What is Pass and RequiredPass when this assertion hits ? I haven't had a chance to explore too deeply yet (the stack trace doesn't give any useful information) but I suspect Pass is the register allocator and RequiredPass is the coalescer. I say that because the coalescer is an ImmutablePass (since it shouldn't...

On Wednesday 25 July 2007 21:35, David A. Greene wrote: > > What is Pass and RequiredPass when this assertion hits ? > > I haven't had a chance to explore too deeply yet (the stack trace doesn't > give any useful information) but I suspect Pass is the register allocator > and RequiredPass is the coalescer. Turns out I was wrong. Pass is the register allocator but...

...the llvm main branch and the poolalloc today in the morning and recompiled everything from scratch : $ opt -load /home/pprabhu/llvm/llvm-install-x86-64/lib/libpoolalloc.so -ds-aa < o.bc opt: /home/pprabhu/llvm/llvm/lib/VMCore/PassManager.cpp:1418: virtual void llvm::MPPassManager::addLowerLevelRequiredPass(llvm::Pass*, llvm::Pass*): Assertion `(P->getPotentialPassManagerType() < RequiredPass->getPotentialPassManagerType()) && "Unable to handle Pass that requires lower level Analysis pass"' failed. 0 opt 0x0000000000a3fcd0 1 opt 0x0000000000a40024 2 lib...

.... when AU.addRequired<CompleteBUDataStructures>(); is called. $ opt -f -load ~/Projects/llvmstuff/opt/poolalloc/lib/ libpoolalloc.dylib -raiseallocs -poolalloc-passing-all-pools - pointercompress llist-noopt.bc -o llist-dp.bc Assertion failed: ((P->getPotentialPassManagerType() < RequiredPass- >getPotentialPassManagerType()) && "Unable to handle Pass that requires lower level Analysis pass"), function addLowerLevelRequiredPass, file ~/Projects/llvmstuff/llvm/lib/VMCore/ PassManager.cpp, line 1418. Any ideas what is going wrong here? /Mattias

Can anyone explain what this means? llvm/include/llvm/PassManagers.h:232: virtual void llvm::PMDataManager::addLowerLevelRequiredPass(llvm::Pass*, llvm::Pass*): Assertion `0 && "Unable to handle Pass that requires lower level Analysis pass"' failed. -Dave

On Jul 25, 2007, at 3:15 PM, David A. Greene wrote: > Can anyone explain what this means? > > llvm/include/llvm/PassManagers.h:232: virtual void > llvm::PMDataManager::addLowerLevelRequiredPass(llvm::Pass*, > llvm::Pass*): > Assertion `0 && "Unable to handle Pass that requires lower level > Analysis > pass"' failed. In simple words, pass manager is not able to schedule passes in requested order. Pass manager is not able to find required pass at the...

On Jul 26, 2007, at 8:01 AM, David Greene wrote: > On Wednesday 25 July 2007 21:35, David A. Greene wrote: > >>> What is Pass and RequiredPass when this assertion hits ? >> >> I haven't had a chance to explore too deeply yet (the stack trace >> doesn't >> give any useful information) but I suspect Pass is the register >> allocator >> and RequiredPass is the coalescer. > > Turns out I w...

...the llvm main branch and the poolalloc today in the morning and recompiled everything from scratch : $ opt -load /home/pprabhu/llvm/llvm-install-x86-64/lib/libpoolalloc.so -ds-aa < o.bc opt: /home/pprabhu/llvm/llvm/lib/VMCore/PassManager.cpp:1418: virtual void llvm::MPPassManager::addLowerLevelRequiredPass(llvm::Pass*, llvm::Pass*): Assertion `(P->getPotentialPassManagerType() < RequiredPass->getPotentialPassManagerType()) && "Unable to handle Pass that requires lower level Analysis pass"' failed. 0 opt 0x0000000000a3fcd0 1 opt 0x0000000000a40024 2 lib...

...alloc today in the morning and recompiled everything from > scratch : > > $ opt -load /home/pprabhu/llvm/llvm-install-x86-64/lib/libpoolalloc.so > -ds-aa < o.bc > > opt: /home/pprabhu/llvm/llvm/lib/VMCore/PassManager.cpp:1418: virtual > void llvm::MPPassManager::addLowerLevelRequiredPass(llvm::Pass*, > llvm::Pass*): Assertion `(P->getPotentialPassManagerType() < > RequiredPass->getPotentialPassManagerType()) && "Unable to handle Pass > that requires lower level Analysis pass"' failed. > 0 opt 0x0000000000a3fcd0 > 1 opt 0...

...U) const { AU.addRequired<AssumptionCacheTracker>(); AU.addRequired<TargetLibraryInfoWrapperPass>();+ AU.addRequired<LoopInfoWrapperPass>(); getAAResultsAnalysisUsage(AU); CallGraphSCCPass::getAnalysisUsage(AU);} I get llvm_unreachable in `void PMDataManager::addLowerLevelRequiredPass(Pass *P, Pass *RequiredPass)' Thanks,-Aditya -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160321/e25708b1/attachment.html>

...lalloc and built without enabling optimizations, on linux x86_64 but when I try to run opt -load=$HOME/src/llvm/projects/poolalloc/Debug/lib/libLLVMDataStructure.so -ds-aa -print-alias-sets -disable-output hello.bc I get opt: PassManager.cpp:1416: virtual void llvm::MPPassManager::addLowerLevelRequiredPass(llvm::Pass*, llvm::Pass*): Assertion `(P->getPotentialPassManagerType() < RequiredPass->getPotentialPassManagerType()) && "Unable to handle Pass that requires lower level Analysis pass"' failed. So my question is whether I am doing something obviously wrong, or other...

Dear All, I'm triggering the following assertion in MPPassManager::addLowerLevelRequiredPass(): assert ((P->getPotentialPassManagerType() < RequiredPass->getPotentialPassManagerType()) && "Unable to handle Pass that requires lower level Analysis pass"); As it turns out, both P and RequiredPass are both ModulePasses. Should the assertion be...

...A; and B does not preserve A. A valid pass ordering would be A B A C. However, opt gives the following assertion: $ opt -load libPassTest.so foo.bc -f -o /dev/null -c -debug-pass=Structure opt: /u/loc/kevin/llvm/llvm/lib/VMCore/PassManager.cpp:1424: virtual void llvm::MPPassManager::addLowerLevelRequiredPass(llvm::Pass*, llvm::Pass*): Assertion `(P->getPotentialPassManagerType() < RequiredPass->getPotentialPassManagerType()) && "Unable to handle Pass that requires lower level Analysis pass"' failed. even though all passes are ModulePasses and do not require lower level p...

...Tracker>(); > AU.addRequired<TargetLibraryInfoWrapperPass>(); > + AU.addRequired<LoopInfoWrapperPass>(); > getAAResultsAnalysisUsage(AU); > CallGraphSCCPass::getAnalysisUsage(AU); > } > > I get llvm_unreachable in `void > PMDataManager::addLowerLevelRequiredPass(Pass *P, Pass *RequiredPass)' > > Thanks, > -Aditya > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An...

...ge (this=0x86f798c, P=0x892bfc0) at <...>/llvm-2.9/lib/VMCore/PassManager.cpp:577 #1 0x08322cfb in llvm::PMTopLevelManager::setLastUser (this=0x86f798c, AnalysisPasses=..., P=0x892d2e0) at <...>/llvm-2.9/lib/VMCore/PassManager.cpp:516 #2 0x083275f5 in llvm::MPPassManager::addLowerLevelRequiredPass (this=0x885cc60, P=0x892d2e0, RequiredPass=0x892bfc0) at <...>/llvm-2.9/lib/VMCore/PassManager.cpp:1608 #3 0x08324cef in llvm::PMDataManager::add (this=0x885cc70, P=0x892d2e0, ProcessAnalysis=true) at <...>/llvm-2.9/lib/VMCore/PassManager.cpp:989 #4 0x08327f11 in llvm::ModulePass::ass...

...s specific to "Module PassManagers", so ideally none of the logic would be used/touched by the FunctionPassManager stuff etc. Given this, it shouldn't be in something generic like the base PassUnit class, which is why I'm talking about it here. :) + std::vector<Pass*> RequiredPasses; Why have the list of required passes here? You can trivially get this from P->getAnalysisUsage(), likewise with the pass name. +public: + PassUnit(Traversal traversal = LINEAR, Pass *Pass) : + traversal(traversal), + + virtual const char *getPMName() const =0; + + virtual const c...

The patch below basically hammers out some ideas as to where I'd like to take the passmanager in LLVM. I've tried thinking things through, but I'm still a n00b, so some criticism would be more than welcome. =) Starting from line 191 down. If you're wondering why I created a patch, well that's because I found thinking in passmanagert.h the most productive. -- Regards.

...92bfc0) at > <...>/llvm-2.9/lib/VMCore/PassManager.cpp:577 > #1 0x08322cfb in llvm::PMTopLevelManager::setLastUser > (this=0x86f798c, AnalysisPasses=..., P=0x892d2e0) at > <...>/llvm-2.9/lib/VMCore/PassManager.cpp:516 > #2 0x083275f5 in llvm::MPPassManager::addLowerLevelRequiredPass > (this=0x885cc60, P=0x892d2e0, RequiredPass=0x892bfc0) at > <...>/llvm-2.9/lib/VMCore/PassManager.cpp:1608 > #3 0x08324cef in llvm::PMDataManager::add (this=0x885cc70, > P=0x892d2e0, ProcessAnalysis=true) at > <...>/llvm-2.9/lib/VMCore/PassManager.cpp:989 > #4 0x083...

...sManagers", so ideally none of the logic would be used/touched by the > FunctionPassManager stuff etc. Given this, it shouldn't be in something > generic like the base PassUnit class, which is why I'm talking about it > here. :) Makes sense. > + std::vector<Pass*> RequiredPasses; > > Why have the list of required passes here? You can trivially get this > from P->getAnalysisUsage(), likewise with the pass name. My idea was to add dependencies as the passes were being organised, such as a functionpass depending upon callgraphscc as part of the traversal bit....

...<...>/llvm-2.9/lib/VMCore/PassManager.cpp:577 >> #1  0x08322cfb in llvm::PMTopLevelManager::setLastUser >> (this=0x86f798c, AnalysisPasses=..., P=0x892d2e0) at >> <...>/llvm-2.9/lib/VMCore/PassManager.cpp:516 >> #2  0x083275f5 in llvm::MPPassManager::addLowerLevelRequiredPass >> (this=0x885cc60, P=0x892d2e0, RequiredPass=0x892bfc0) at >> <...>/llvm-2.9/lib/VMCore/PassManager.cpp:1608 >> #3  0x08324cef in llvm::PMDataManager::add (this=0x885cc70, >> P=0x892d2e0, ProcessAnalysis=true) at >> <...>/llvm-2.9/lib/VMCore/PassManager.cp...