Displaying 3 results from an estimated 3 matches for "immutablemachinefunctionpass".
2007 Jul 25
2
[LLVMdev] PassManager Error
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
2007 Jul 25
0
[LLVMdev] PassManager Error
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
2007 Jul 26
2
[LLVMdev] PassManager Error
...oalescer> to talk to the coalescer.
So now the question is, what kind of Pass should the coalescer be? It should
not be run by PassManager but PassManager still needs to know about its
analysis requirements. Do we need a new kind of Pass, like
ImmutableFunctionPass, or in this specific case, ImmutableMachineFunctionPass?
I hate this kind of multiple-cross-product-derivation-categorization. :-/
How does this work for AliasAnalysis, which is also an ImmutablePass (or, at
least some of them are)? How do FunctionPasses query the analysis?
-Dave