search for: graphtype

...) to MachineInstrIterator.h to iterate over machine instructions in a machine function. But the build is throwing the following error: llvm[2]: Compiling MC_DFG.cpp for Debug+Asserts build /home/abhi/work/llvm31/llvm/include/llvm/Support/GraphWriter.h: In member function ‘void llvm::GraphWriter<GraphType>::writeNodes() [with GraphType = llvm::MCDFGraph<llvm::MachineFunction*>]’: /home/abhi/work/llvm31/llvm/include/llvm/Support/GraphWriter.h:100: instantiated from ‘void llvm::GraphWriter<GraphType>::writeGraph(const std::string&) [with GraphType = llvm::MCDFGraph<llvm::MachineF...

...o > iterate over machine instructions in a machine function. But the build is > throwing the following error: > > llvm[2]: Compiling MC_DFG.cpp for Debug+Asserts build > /home/abhi/work/llvm31/llvm/include/llvm/Support/GraphWriter.h: In member > function ‘void llvm::GraphWriter<GraphType>::writeNodes() [with GraphType = > llvm::MCDFGraph<llvm::MachineFunction*>]’: > /home/abhi/work/llvm31/llvm/include/llvm/Support/GraphWriter.h:100: > instantiated from ‘void llvm::GraphWriter<GraphType>::writeGraph(const > std::string&) [with GraphType = llvm::MCDFGra...

...9-06 17:30, Ioannis Nousias wrote: >>> >>> >>>> I've tried to write a DFGPrinter based on the CFGPrinter, as you >>>> suggested, but encountered problems. >>>> >>>> The GraphWriter expects >>>> GraphTraits<GraphType>::nodes_begin()/nodes_end(). The way this is >>>> implemented in CFG.h, a function is a graph of basic blocks. A >>>> GraphTraits<Function*> inherits from GraphTraits<BasicBlock*>, and >>>> implements those nodes_begin()/nodes_end() wrapper functi...

...; > Török Edwin wrote: >> On 2009-09-06 17:30, Ioannis Nousias wrote: >> >>> I've tried to write a DFGPrinter based on the CFGPrinter, as you >>> suggested, but encountered problems. >>> >>> The GraphWriter expects >>> GraphTraits<GraphType>::nodes_begin()/nodes_end(). The way this is >>> implemented in CFG.h, a function is a graph of basic blocks. A >>> GraphTraits<Function*> inherits from GraphTraits<BasicBlock*>, and >>> implements those nodes_begin()/nodes_end() wrapper functions. Should...

...ction to SCCIterator.h. This function is now removed. This patch makes the following changes: 1. Allow SCCIterator to work with GraphT types that are constant. 2. Allow SCCIterator to work with inverse graphs. 3. Fix an incorrect comment in GraphTraits.h (the type in the comment was given as GraphType* when it is actually const GraphType &). I think these changes should be pretty uncontroversial. Would someone with commit authority please apply this for me? --Patrick Index: include/llvm/ADT/SCCIterator.h =================================================================== --- include/llv...

...clude/llvm/ADT/GraphTraits.h (revision 76093) +++ include/llvm/ADT/GraphTraits.h (working copy) @@ -30,7 +30,7 @@ // typedef NodeType - Type of Node in the graph // typedef ChildIteratorType - Type used to iterate over children in graph - // static NodeType *getEntryNode(GraphType *) + // static NodeType *getEntryNode(const GraphType &) // Return the entry node of the graph // static ChildIteratorType child_begin(NodeType *)

I've tried to write a DFGPrinter based on the CFGPrinter, as you suggested, but encountered problems. The GraphWriter expects GraphTraits<GraphType>::nodes_begin()/nodes_end(). The way this is implemented in CFG.h, a function is a graph of basic blocks. A GraphTraits<Function*> inherits from GraphTraits<BasicBlock*>, and implements those nodes_begin()/nodes_end() wrapper functions. Should I modify CFG.h and make now BasicBl...

On 2009-09-06 17:30, Ioannis Nousias wrote: > I've tried to write a DFGPrinter based on the CFGPrinter, as you > suggested, but encountered problems. > > The GraphWriter expects > GraphTraits<GraphType>::nodes_begin()/nodes_end(). The way this is > implemented in CFG.h, a function is a graph of basic blocks. A > GraphTraits<Function*> inherits from GraphTraits<BasicBlock*>, and > implements those nodes_begin()/nodes_end() wrapper functions. Should I > modify CFG.h...

On Aug 6, 2009, at 4:19 PM, Patrick Alexander Simmons wrote: > Chris Lattner wrote: >> On Aug 4, 2009, at 3:48 PM, Patrick Alexander Simmons wrote: >> >> >>> Hi, >>> >>> I've been using scc_iterator, and I added the templates necessary to >>> make it work with inverse graphs. I also added a "bb_reachable" >>>

...(revision 76093) > +++ include/llvm/ADT/GraphTraits.h (working copy) > @@ -30,7 +30,7 @@ > // typedef NodeType - Type of Node in the graph > // typedef ChildIteratorType - Type used to iterate over children in > graph > > - // static NodeType *getEntryNode(GraphType *) > + // static NodeType *getEntryNode(const GraphType &) > // Return the entry node of the graph > > // static ChildIteratorType child_begin(NodeType *) > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu...

Hi Ioannis, On Thu, 2009-08-13 at 19:31 +0100, Ioannis Nousias wrote: > Thanks Tobi for the tip. > > however I also need the Data-Flow-Graph of each basic block/functions. > As I said, I need a view of how the instructions 'link' to each other > (via registers or memory aliasing or whatnot) I believe that there is not yet a DOT printer for this kind of information.

Chris Lattner wrote: > On Aug 4, 2009, at 3:48 PM, Patrick Alexander Simmons wrote: > > >> Hi, >> >> I've been using scc_iterator, and I added the templates necessary to >> make it work with inverse graphs. I also added a "bb_reachable" >> function to tell whether an arbitrary graph node is part of cycle. >> Might this be useful to

...?). inline comments follow... Török Edwin wrote: > On 2009-09-06 17:30, Ioannis Nousias wrote: > >> I've tried to write a DFGPrinter based on the CFGPrinter, as you >> suggested, but encountered problems. >> >> The GraphWriter expects >> GraphTraits<GraphType>::nodes_begin()/nodes_end(). The way this is >> implemented in CFG.h, a function is a graph of basic blocks. A >> GraphTraits<Function*> inherits from GraphTraits<BasicBlock*>, and >> implements those nodes_begin()/nodes_end() wrapper functions. Should I >&g...

Hi I'm trying to get a graphviz output (DOT) of a code I'm compiling. I want to see the DFG/CFG of the LLVM assembly, how the operations are chained together. The documentation mentions something about calling certain methods from within gdb, but isn't there some option when invoking the compiler (I've seen some -print-cfg and -dot-cfg options mentioned in some source files,