search for: piobj

...: Argument 'help' defined more than once! opt: CommandLine Error: Argument 'help-hidden' defined more than once! opt: CommandLine Error: Argument 'version' defined more than once! opt: Pass.cpp:346: void llvm::RegisterPassBase::registerPass(): Assertion `PassInfoMap->find(PIObj.getTypeInfo()) == PassInfoMap->end() && "Pass already registered!"' failed. Aborted PASS: virtual bool runOnFunction(Function &F) { bool change= false; Function* func = &F; for(Function::iterator it = func->begin(), ite = func ->end(); it!=ite ; ++...

...rk at all. Oh, I guess this clase in RegisterAGBase's constructor takes care of it: InterfaceInfo = const_cast<PassInfo*>(Pass::lookupPassInfo(InterfaceID)); if (InterfaceInfo == 0) { // First reference to Interface, register it now. registerPass(); InterfaceInfo = &PIObj; } Is that right? This PassManager stuff is extremely confusing and not well documented. Does it really buy us all that much? I can't believe there's much room for rescheduling passes unless llvm actually reschedules optimizations, which would be *very* bad indeed. Otherwise, isn...

On Friday 14 September 2007 15:51, Chris Lattner wrote: > When basicaa registers itself as part of the analysis group, it uses: > > RegisterPass<BasicAliasAnalysis> > X("basicaa", "Basic Alias Analysis (default AA impl)"); > > // Declare that we implement the AliasAnalysis interface > RegisterAnalysisGroup<AliasAnalysis, true> Y(X);

...n RegisterAGBase's constructor takes care of it: > > InterfaceInfo = const_cast<PassInfo*>(Pass::lookupPassInfo > (InterfaceID)); > if (InterfaceInfo == 0) { > // First reference to Interface, register it now. > registerPass(); > InterfaceInfo = &PIObj; > } > > Is that right? Yes. > This PassManager stuff is extremely confusing and not well documented. Hrm? http://llvm.org/docs/WritingAnLLVMPass.html > Does > it really buy us all that much? Yes. > I can't believe there's much room for > rescheduling passes...