search for: graphwriter

...ate <> struct GraphTraits<DFG<Function*> >*) 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::strin...

I tried debugging it and the issue seems to be in the implementation of MachineInstrIterator.h and the way it interacts with GraphWriter.h functions. I found this by replacing the ( template <> struct GraphTraits<MCDFGraph<MachineFunction*> >) with a similar MCDFGraph based template of CFG similar to the one in MachineFunction.h (similarly replacing the DOTGraphTraits with the one for CFG) and it works and pops up...

...ö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 >>>> impleme...

Issue: GraphWriter includes <ostream>, which my gcc2 apparently thinks is <ostream.h>. Fix: Make a new <Support/ostream> that handles this discrepancy, ala <Support/hash_set>. -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69 -------------- next part -------------- An...

Hi. I'd like to know where LLVM installs the GraphWriter.h file on a standard install. I'd like to know this to avoid any possibility of overwriting it with software that I am developing. Please CC me as I'm off list. Thanks! Paul Blackburn

...s works fine except that I have no clue how to support (a) and (b) since once the destination node is returned I lose access to the edge and cannot do any text annotation onto an edge of the graph. Is there some other way to achieve (a) and (b) without having to implement my own special version of GraphWriter ? thanks, Prakash

...n*>. > > 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_...

...I have no clue how to support (a) > and (b) since once the destination node is returned I lose access to > the edge and cannot do any text annotation onto an edge of the graph. > > Is there some other way to achieve (a) and (b) without having to > implement my own special version of GraphWriter ? > > thanks, > Prakash > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Also sprach Casey Carter: } Issue: GraphWriter includes <ostream>, which my gcc2 apparently thinks } is <ostream.h>. } Fix: Make a new <Support/ostream> that handles this discrepancy, ala } <Support/hash_set>. } Um...was it entirely necessary to issue *8* email messages to the group with mostly single-line fixes inste...

I've been doing some experiments with the Boost Graph Library (BGL) and interfacing to llvm's GraphWriter system. I'm using GBL for some custom work and needed a way to hook BGL's write_graphviz into GraphWriter to use the existing display infrastructure. To do this I added a HAVE_BOOST configure item and #ifdef'd the Boost support code in GraphWriter. Is this useful to anyone else? Is...

...since once the destination node is returned I lose access to >>> the edge and cannot do any text annotation onto an edge of the >>> graph. >>> >>> Is there some other way to achieve (a) and (b) without having to >>> implement my own special version of GraphWriter ? >>> >>> thanks, >>> Prakash >>> _______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>...

...to support (a) >> and (b) since once the destination node is returned I lose access to >> the edge and cannot do any text annotation onto an edge of the graph. >> >> Is there some other way to achieve (a) and (b) without having to >> implement my own special version of GraphWriter ? >> >> thanks, >> Prakash >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > __________________________...

Also sprach Casey Carter: } Bill? Wendling wrote: } } >Um...was it entirely necessary to issue *8* email messages to the group } >with mostly single-line fixes instead of just one email with all of the } >fixes and an explanation for each? } > } > } > } Actually, yes it was. Proper netiquette when submitting to a technical } list is to have a single topic per message. This

Bill? Wendling wrote: >Also sprach Casey Carter: >} Issue: GraphWriter includes <ostream>, which my gcc2 apparently thinks >} is <ostream.h>. >} Fix: Make a new <Support/ostream> that handles this discrepancy, ala >} <Support/hash_set>. >} >Um...was it entirely necessary to issue *8* email messages to the group >with mostly...

...-page is stating that the file name has to come before all arguments and the --spartan is actually -spartan. I don't know for newer versions of gv. The attached patch fixes that for me. Please apply if appropriate. thanks, Patrick. -------------- next part -------------- Index: lib/Support/GraphWriter.cpp =================================================================== --- lib/Support/GraphWriter.cpp (revision 62576) +++ lib/Support/GraphWriter.cpp (working copy) @@ -57,8 +57,8 @@ sys::Path gv(LLVM_PATH_GV); args.clear(); args.push_back(gv.c_str()); - args.push_back("--...

...dentified with hexadecimal addresses. For example, an edge from one block to another may look like: Node0x10026b0:s0 -> Node0x1004c20; I've been trying to figure out where these hexadecimal addresses come from. I've been up and down the code but remain at a loss. I can see where GraphWriter.h is actually writing the strings to the DOT file, and I can see that some of the DOT data is coming from DOTGraphTraits in CFGPrinter.h. But the hexadecimal addresses are a mystery. I thought perhaps a BasicBlock method, such as getName, might be producing the addresses, but no. Can anyon...

Hi all, I need to look at the CFG of a loop during debugging. However the containing function is very large, so it is rather difficult to use the CFG of the complete function. I tried using the ViewGraph method, but the compiler kept complaining about undefined symbols related to GraphTraits or DOTGraphTraits. Is there any example that I could look at to find out, what exactly I need to call

...___________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev I don't know if anyone has already done this, but some important pieces are there. See Dataflow.h and GraphWriter.h. I think you'll run into a problem though because the value graph isn't fully connected. You have to walk the instruction stream looking for "roots". -Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-...

...0]% cvs update cvs update: Updating . ? gnumake.out cvs update: Updating Support cvs update: Updating include cvs update: Updating include/Support cvs update: cannot close BitSetVector.h: No space left on device cvs update: could not check out include/Support/BitSetVector.h cvs update: cannot close GraphWriter.h: No space left on device cvs update: could not check out include/Support/GraphWriter.h cvs update: cannot close TarjanSCCIterator.h: No space left on device cvs update: could not check out include/Support/TarjanSCCIterator.h cvs update: cannot close hash_map: No space left on device cvs update: c...

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...