search for: callgraphscc

Hello, I want to access the instructions via: CallGraph->CallGraphNode->Function->BB->Instruction Is this possible? Right now, I'm iterating over the CallGraph Nodes via CallGraphSCC:iterator, but then I have to cast that iterator to a CallGraphNode const and then when I call CallGraphNode->getFunction, it returns a valid function but seg faults on function->getName()? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.o...

In the documentation, it says that a module pass can not require a function pass. Is it also true that a CallGraphSCC pass can not require a function pass? Ryan

Hi,   I have read through the discussion on, using LoopInfo in functionPass and LoopPass and ModulePass, but I think I have a different situation.   I have to run an optimization as "CallGraphSCC Pass". In this pass, I can traverse through the function and basic block from SCC, but my requirement is to have loop Information as well in this.   I need information about whether an instruction (in a basic block) resides in a loop and what is the corresponding loop depth? (I have seen posts...

The following code is causing an "UNREACHABLE executed!" and a stack dump, any ideas? namespace { struct myPass : public CallGraphSCCPass { static char ID; myPass() : CallGraphSCCPass(ID) {} virtual void getAnalysisUsage(AnalysisUsage &AU) const { AU.setPreservesAll(); AU.addRequired<LoopInfo>(); } virtual bool runOnSCC(CallGraphSCC &SCC) { for (CallGraphSCC::iterator CGNodeItr...

I would have thought this would have been possible. On Thu, Nov 17, 2011 at 3:49 PM, Ryan Taylor <ryta1203 at gmail.com> wrote: > So is this simply not possible? > > > On Thu, Nov 17, 2011 at 10:31 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > >> Nick, >> >> Thanks for this info, though this didn't help my problem at all. >> >>

Hi all, I am experimenting to run a pass inherited from CallGraphSCCPass. In the pass, I iterate all functions in a SCC. In each iteration, I access all arguments of a function in the following way: Function::arg_iterator PI = fun->arg_begin(), PE = fun->arg_end(); ... I have no trouble with building. However, I am troubled with "segmentation fault...

On Tue, Nov 29, 2011 at 6:59 PM, Ryan Taylor <ryta1203 at gmail.com> wrote: > The following code is causing an "UNREACHABLE executed!" and a stack dump, > any ideas? The stack might be handy. > namespace { >   struct myPass : public CallGraphSCCPass { >   static char ID; >   myPass() : CallGraphSCCPass(ID) {} >   virtual void getAnalysisUsage(AnalysisUsage &AU) const { >            AU.setPreservesAll(); >            AU.addRequired<LoopInfo>(); >   } >   virtual bool runOnSCC(CallGraphSCC &SCC) { >     ...

...pPass Ryan, See http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-November/045423.html - Devang On Nov 29, 2011, at 6:59 PM, Ryan Taylor wrote: > The following code is causing an "UNREACHABLE executed!" and a stack dump, any ideas? > > namespace { >  struct myPass : public CallGraphSCCPass { >  static char ID; >  myPass() : CallGraphSCCPass(ID) {} >  virtual void getAnalysisUsage(AnalysisUsage &AU) const { >            AU.setPreservesAll(); >            AU.addRequired<LoopInfo>(); >  } >  virtual bool runOnSCC(CallGraphSCC &SCC) { >        fo...

...T will manage +// all passes as one, rather than having any sort of hierarchy. The trick is +// to have all the passes wrapped into a single abstract PassUnit. Each +// PassUnit will then have concrete implmentations for all the various +// passes, such as, module, function, basicblock, loop, callgraphscc, and +// immutable. These PassUnit will provide a single point of entry as an +// interface while its concrete implementations will handle all the pass +// specific details. Then a two types of PassCollection will be required, +// one ordered and another unordered. This will allow either batc...

...n Tue, Nov 29, 2011 at 6:59 PM, Ryan Taylor <ryta1203 at gmail.com> wrote: > > The following code is causing an "UNREACHABLE executed!" and a stack > dump, > > any ideas? > > The stack might be handy. > > > namespace { > > struct myPass : public CallGraphSCCPass { > > static char ID; > > myPass() : CallGraphSCCPass(ID) {} > > virtual void getAnalysisUsage(AnalysisUsage &AU) const { > > AU.setPreservesAll(); > > AU.addRequired<LoopInfo>(); > > } > > virtual bool runOnSCC...

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.

...l/llvmdev/2011-November/045423.html > > - > Devang > > On Nov 29, 2011, at 6:59 PM, Ryan Taylor wrote: > > > The following code is causing an "UNREACHABLE executed!" and a stack > dump, any ideas? > > > > namespace { > > struct myPass : public CallGraphSCCPass { > > static char ID; > > myPass() : CallGraphSCCPass(ID) {} > > virtual void getAnalysisUsage(AnalysisUsage &AU) const { > > AU.setPreservesAll(); > > AU.addRequired<LoopInfo>(); > > } > > virtual bool runOnSCC(Call...

Yes, this is pretty unacceptable IMHO. I would go revert crazy if I knew what to hit, unfortunately I don't. Currently I believe there are two problems, a CallGraphSCC assert which is firing everywhere (including the clang test suite, *cough*). This started with 80698. Chris is working on this (if it isn't already fixed). The bootstrap comparison failures are being looked at by Devang. - Daniel On Tue, Sep 1, 2009 at 1:54 PM, Stuart Hastings<stuart at...

Hi all, I am experimenting to run a pass inherited from CallGraphSCCPass. In the pass, I iterate all functions in a SCC. In each iteration, I access all arguments of a function in the following way: Function::arg_iterator PI = fun->arg_begin(), PE = fun->arg_end(); ... I have no trouble with building. However, I am troubled with "segmentation fault...

I'm building a SCCPass below, it appears that the CallGraphNode->getFunction returns a valid function but seg faults on call like "getName" or "size" but not on calls like "empty" (which returns false). My understanding is that the heirarchy is: CallGraphSCC->CallGraphNode->Function->BasicBlock->Instruction, is this not the case? virtual bool runOnSCC(CallGraphSCC &SCC) { errs() << "CDFGPass: " << "\n"; errs() <<"Size of SCC: "<<SCC.size()<<"\n";...

Hi, I am trying to write my own command-line tool which would use alias analysis in a CallGraphSCCPass. Firstly, I inherit a class AnalysisDriver from CallGraphSCCPass. Then, I implement my own runOnFunction method which tries to get alias analysis from each function. The code is shown as follows: *class AnalysisDriver : public CallGraphSCCPass {* * static char Pid;* * PassManager &pass...

...egacy structure of skipFunction()/Module(), put skippability check in each single pass for new pass manager. Or since there is no optnone support, we now may also create label on each pass to determine it is skippable or not, and then do the check at pass manager level. 3. No region/basicblock/callgraphscc pass support for new pass manager? In legacy pass manager, OptBisect will be checked by skip() function on certain types of passes. like skipRegion(), skipBasicBlocks(). But I did not see implementations of the passes I mentioned above in new passes. So any plan to have them any more? 4. I...

In order to detect whether CallSite is present in innermost loop, do I need to insert logic from LoopInfo pass for collecting loops, within a CallGraphSCC pass?   Is there any other approach for this?   Regards, Pankaj -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111116/cd9d51b7/attachment.html>

...t; Can someone verify this behavior? > Any tips on how I should go about extending the class in order to > visit > all SCCs? > Is it desirable to augment the scc_iterator class itself, or should I > construct another one? The change in behavior may impact things such > as > CallGraphSCCPass, GlobalsModRef, etc. and I don't know if it is > desirable to have that change there. This definitely sounds bad, but doesn't match what I'm seeing with the callgraphscc passmanager. How are you using SCCIterator? -Chris

The buildbots are unhappy again. :-( Specifically, the "llvm-gcc-i386-darwin9" buildbot here at Apple last compiled TOT successfully yesterday morning (31aug); that was revision 80586. By revision 80589, the bootstrap failed due to a miscompare, and by revision 80610, it's aborting while compiling little pieces of libgcc. 80586 built O.K. (about 8AM, Pacific Standard