search for: addtopassmanag

...ude/llvm/Pass.h:264: warning: `virtual bool llvm::FunctionPass::run(llvm::Module&)' was hidden ../../../include/llvm/Pass.h:326: warning: by `bool llvm::BasicBlockPass::run(llvm::BasicBlock&)' ../../../include/llvm/Pass.h:275: warning: `virtual void llvm::FunctionPass::addToPassManager(llvm::PassManagerT<llvm::Module>*, llvm::AnalysisUsage&)' was hidden ../../../include/llvm/Pass.h:332: warning: by `virtual void llvm::BasicBlockPass::addToPassManager(llvm::PassManagerT<llvm::BasicBlock>*, llvm::AnalysisUsage&)' The problem is that &quot...

...arning: `virtual bool > llvm::FunctionPass::run(llvm::Module&)' was hidden > ../../../include/llvm/Pass.h:326: warning: by `bool > llvm::BasicBlockPass::run(llvm::BasicBlock&)' > ../../../include/llvm/Pass.h:275: warning: `virtual void > llvm::FunctionPass::addToPassManager(llvm::PassManagerT<llvm::Module>*, > llvm::AnalysisUsage&)' was hidden > ../../../include/llvm/Pass.h:332: warning: by `virtual void > llvm::BasicBlockPass::addToPassManager(llvm::PassManagerT<llvm::BasicBlock>*, > llvm::AnalysisUsage&)' > &gt...

...ing: `virtual bool > llvm::FunctionPass::run(llvm::Module&)' was hidden > ../../../include/llvm/Pass.h:326: warning: by `bool > llvm::BasicBlockPass::run(llvm::BasicBlock&)' > ../../../include/llvm/Pass.h:275: warning: `virtual void > llvm::FunctionPass::addToPassManager(llvm::PassManagerT<llvm::Module>*, > llvm::AnalysisUsage&)' was hidden > ../../../include/llvm/Pass.h:332: warning: by `virtual void > llvm::BasicBlockPass::addToPassManager(llvm::PassManagerT<llvm::BasicBlock>*, > llvm::AnalysisUsage&)' >...

...; > llvm::FunctionPass::run(llvm::Module&)' was hidden > > ../../../include/llvm/Pass.h:326: warning: by `bool > > llvm::BasicBlockPass::run(llvm::BasicBlock&)' > > ../../../include/llvm/Pass.h:275: warning: `virtual void > > llvm::FunctionPass::addToPassManager(llvm::PassManagerT<llvm::Module>*, > > llvm::AnalysisUsage&)' was hidden > > ../../../include/llvm/Pass.h:332: warning: by `virtual void > > llvm::BasicBlockPass::addToPassManager(llvm::PassManagerT<llvm::BasicBlock>*, > > llvm::AnalysisUsage...

...entual rewrite does occur. Here's what I see: We have a modulepass MP that needs a functionpass FP. We need a copy of that FP (and every pass it depends on) for each function in the module that MP is being run on. Currently, in add() we only create one instance of FP, on which we then call addToPassManager() so we can get the right call to addPass(FP, ...), which adds FP to a single Batcher, in this case, a PassManagerT<FunctionPass>. In addPass(MP, ...) we see the FP in the required set, and attempt to mark it as used by the MP. We don't find it in markPassUsed though, because FP was...

...o -help > Error opening > '/Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so': Can't > open :/Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so: > dlopen(/Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so, 9): > Symbol not found: > __ZN4llvm12FunctionPass16addToPassManagerEPNS_20FunctionPassManagerTERNS_13AnalysisUsageE > Referenced > from: /Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so > Expected in: flat namespace This corresponds to: FunctionPass::addToPassManager(llvm::FunctionPassManagerT*, llvm::AnalysisUsage&) which should be linked...

...ild-ppc/Release/lib/LLVMHello.so -help Error opening '/Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so': Can't open :/Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so: dlopen(/Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so, 9): Symbol not found:__ZN4llvm12FunctionPass16addToPassManagerEPNS_20FunctionPassManagerTERNS_13AnalysisUsageE Referenced from: /Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so Expected in: flat namespace pollux:~/tools/build-ppc/Release/lib jingyu$ nm libLLVMCore.a | grep __ZN4llvm12FunctionPass16addToPassManagerEPNS_20FunctionPassManagerTERNS_13...

On Thu, 5 Aug 2004, Michael McCracken wrote: > > You're right that FunctionPass's are not supposed to have state > > (something that many people overlook :) ), however, for now, nothing > > will break if it does have state, and this is really the only way > > around this. > > I'm not sure if I can do this. The pass I'm writing is writing info >

...ld-ppc/Release/lib/LLVMHello.so -help Error opening '/Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so': Can't open :/Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so: dlopen(/Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so, 9): Symbol not found: __ZN4llvm12FunctionPass16addToPassManagerEPNS_20FunctionPassManagerTERNS_13AnalysisUsageE Referenced from: /Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so Expected in: flat namespace I guess the problem is that the library who implements the symbol was not found at run time, or the lib path information was not given to LLVMH...

On Aug 5, 2004, at 5:30 PM, Chris Lattner wrote: > On Thu, 5 Aug 2004, Michael McCracken wrote: > >> Hi, I have a hopefully quick question. I'm writing a Pass that needs >> to >> see a whole module at a time and keep some state, so I subclassed >> Pass. >> However, I want to be able to see the Loops in each Function. Roughly, > > ok. > >>

...> Here's what I see: We have a modulepass MP that needs a functionpass > FP. We need a copy of that FP (and every pass it depends on) for each > function in the module that MP is being run on. Yup. > Currently, in add() we only create one instance of FP, on which we then > call addToPassManager() so we can get the right call to addPass(FP, > ...), which adds FP to a single Batcher, in this case, a > PassManagerT<FunctionPass>. In addPass(MP, ...) we see the FP in the > required set, and attempt to mark it as used by the MP. We don't find > it in markPassUsed though...