search for: isanalysis

Hi, I was looking at the LoopInfo Analysis pass as an example, and found it defined the isAnalysis() method to return true. I assumed the method was overriden from some superclass (Pass, probably) and present in all analysis passes. However, a better look turns out that the method isn't really used anywhere. PassInfo does define the same method which is used, but PassInfo is not a superclas...

On Thursday 25 February 2010 19:24:30 Trevor Harmon wrote: > Hi, > > I'm confused about the is_analysis parameter of the RegisterPass > constructor (defined in PassSupport.h). The only explanation I can > find is that is_analysis should be set to true if the pass is "an > analysis pass, for example dominator tree pass". Can someone please > clarify what is meant

On Fri, Feb 26, 2010 at 05:22:49PM -0800, Trevor Harmon wrote: > On Feb 25, 2010, at 5:45 PM, David A. Greene wrote: > > > The RegisterPass template takes care of notifying the PassManager > > that the pass exists. One of the advantages of PassManager is > > that it decouples pass execution from the rest of the infrastructure > > so the class need not be visible to

On Feb 26, 2010, at 7:42 PM, Tom Prince wrote: > You cannot refer to anything in anonymous namespace by name from > another file, however, if you have a pointer, say, then you can > still use the > pointer. Yes, that would make sense, except I don't see any pointers being passed. The relevant line in lib/Transforms/Hello.cpp is: static RegisterPass<Hello>

On Feb 25, 2010, at 5:45 PM, David A. Greene wrote: > The RegisterPass template takes care of notifying the PassManager > that the pass exists. One of the advantages of PassManager is > that it decouples pass execution from the rest of the infrastructure > so the class need not be visible to anything outside the > implementation > of the pass itself. Even though the

Hi, I'm confused about the is_analysis parameter of the RegisterPass constructor (defined in PassSupport.h). The only explanation I can find is that is_analysis should be set to true if the pass is "an analysis pass, for example dominator tree pass". Can someone please clarify what is meant by "analysis pass"? Also -- and this is more of a C++ question than an

I'm getting a lot of these from TOT make: /Volumes/MacOS9/gcc/llvm/include/llvm/Analysis/LoopInfo.h: In instantiation of 'llvm::LoopInfoBase<llvm::BasicBlock>': /Volumes/MacOS9/gcc/llvm/include/llvm/Analysis/LoopInfo.h:886: instantiated from here /Volumes/MacOS9/gcc/llvm/include/llvm/Analysis/LoopInfo.h:573: warning: 'class

...ror. If following helps, please apply. Thanks, - Devang Index: LoopInfo.h =================================================================== --- LoopInfo.h (revision 48476) +++ LoopInfo.h (working copy) @@ -580,9 +580,6 @@ LoopInfoBase() { } ~LoopInfoBase() { releaseMemory(); } - /// isAnalysis - Return true if this pass is implementing an analysis pass. - virtual bool isAnalysis() const { return true; } - void releaseMemory() { for (typename std::vector<LoopBase<BlockT>* >::iterator I = TopLevelLoops.begin(), E = TopLevelLoops.end(); I != E; ++I) @@ -...

...t you need to know is that these classes are going away, and are being replaced with a new macro INITIALIZE_PASS(). I will be applying this change to LLVM HEAD shortly. You can update you code as follows: static RegisterPass<GVN> X("arg", "My Pass's Name", CFGOnly, IsAnalysis); becomes: INITIALIZE_PASS(GVN, "arg", "My Pass's Name", CFGOnly, IsAnalysis); For the moment, these are equivalent, but as the work progresses on this front, RegisterPass will go away and INITIALIZE_PASS will be changed to expand to the right thing for the new system Th...