search for: viewgraph

Hi, I am trying to use the viewGraph() method of SelectionDAG, of course I installed graghviz, nuked my build directory, reconfigured and rebuilt the project. However, gdb does not consistently recognize SelectionDAG::viewgraph(), some times it finds it and some times it says that llvm::SelectionDAG does not have viewGraph(). It worke...

...inding DAG, it complains about not finding viewGragh() in DAG. A. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner Sent: Wednesday, September 26, 2007 12:03 PM To: LLVM Developers Mailing List Subject: Re: [LLVMdev] viewGraph On Wed, 26 Sep 2007 Alireza.Moshtaghi at microchip.com wrote: > I am trying to use the viewGraph() method of SelectionDAG, of course I > installed graghviz, nuked my build directory, reconfigured and rebuilt > the project. However, gdb does not consistently recognize > SelectionDAG::vi...

On Wed, 26 Sep 2007 Alireza.Moshtaghi at microchip.com wrote: > I am trying to use the viewGraph() method of SelectionDAG, of course I > installed graghviz, nuked my build directory, reconfigured and rebuilt > the project. However, gdb does not consistently recognize > SelectionDAG::viewgraph(), some times it finds it and some times it says > that llvm::SelectionDAG does not have v...

> Oh, I tried that, in my previous email, I meant to write: > this->DAG.viewGragh() > DAG.viewGragh() > sorry for the typo in my email... > It does not complain about not finding DAG, it complains about not > finding viewGragh() in DAG. Gragh or Graph. Don't you mean viewGraph() ? Aaron

...e operands: > 0x3922c50, > 0x3913dd0 and 0x38dc530. And <multiple use> seems to mean a node > that feeds > many nodes. > > Is this understanding correct? I think so, though I don't actually look at the SelectionDAG dump() output very often. I highly recommend the viewGraph() output. -view-isel-dags and -view-sched-dags show the graph before and after selection, respectively. See the CodeGen docs where I recently added some text describing all these options. Also, you can call viewGraph() from within a debugger, to view the graph at arbitrary point in the middle of...

Hi list, On my system I have gv 3.5.8 and it does not like to be called with --spartan before the <filename>. The man-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

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 something like ViewGraph(loop, "CFG") ? Martin

Hi, I tried to view the CFG when debugging a pass by "gdb opt," but the gdb does not have DAG.viewGraph function, which is indicated at http://www.llvm.org/docs/ProgrammersManual.html#ViewGraph. Could anyone tell me how to make DAG* functions available in gdb? Thanks in advance. Lu

I'm debugging some X86 patterns and I want to understand the debug dumps from isel better. Here's some example output: 0x391bc40: i64,ch = load 0x3922c50, 0x391b8d0, 0x38dc530 <0x39053e0:0> <sext i32> alignment=4 srcLineNum= 10 0x3922c50: <multiple use> 0x391bc40: <multiple use> 0x3856ab0: <multiple use> 0x3914520: i64 =

On Thursday 02 October 2008 15:37, Dan Gohman wrote: > I highly recommend the viewGraph() output. -view-isel-dags and > -view-sched-dags show the graph before and after selection, > respectively. See the CodeGen docs where I recently added some > text describing all these options. Yeah, I've been using those but they're real hard to understand with big graphs. &gt...

...per >> function to call, I need to know the return type and type of arguments 1 and >> 2. I need to know this pre soft float lowering. >> >> From what I can see, in the beginning of ISelLowering code, the DAG will >> still reflect the original prototype. If I do a DAG.viewGraph() there in the >> debugger, it knows about the proper prototype (pre soft float lowering). >> >> It would have been cool to get the function class that corresponds to this >> call and get the arguments that way but I don't see how I can get it. >> >> Is looki...

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,

..., I need to know the return type and type of arguments 1 >>> and >>> 2. I need to know this pre soft float lowering. >>> >>> From what I can see, in the beginning of ISelLowering code, the DAG will >>> still reflect the original prototype. If I do a DAG.viewGraph() there in >>> the >>> debugger, it knows about the proper prototype (pre soft float lowering). >>> >>> It would have been cool to get the function class that corresponds to >>> this >>> call and get the arguments that way but I don't see ho...

...tain 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, but I can't find which tool supports > them) This should help: http://llvm.org/docs/ProgrammersManual.html#ViewGraph > > Also, LLVM-TV seems outdated. I've tried to compile it with 2.5 LLVM > and > got various errors due to API changes. Tried to correct them, but got > overwhelmed. Has the project been abandoned? Yes, it is really really old and abandoned. -Chris

...DAG. One great way of doing it is through Dot as described in the docs. However, in my case the llvm source code is installed on a remote linux machine and I am accessing it through a Windows PC. So the "popping out" of graphs is not possible. Is there a way that I can dump the output of viewGraph() in a file and run dot over it offline and then copy the final pictures to my windows machine to have some idea about the SelectionDAG. Also, can someone please point me to a location in source code where selectionDAG is traversed. So that I may use similar code to traverse and know about the s...

...nfo": Do you know the following two links? http://llvm.org/releases/3.0/docs/ProgrammersManual.html#DEBUG You can find some example debug code e.g. in method Select(SDNode *Node) in source file lib/Target/MSP430/MSP430ISelDAGToDAG.cpp http://llvm.org/releases/3.0/docs/ProgrammersManual.html#ViewGraph (and the -view… options in http://llvm.org/releases/3.0/docs/CodeGenerator.html#selectiondag_process) This takes some minimal effort to setup but is incredibly useful: Run llc with all -view… options on. This will get you a first idea on where the problem occurs. Then if you find the causing Select...

...to call a helper function, and which helper function to call, I need to know the return type and type of arguments 1 and 2. I need to know this pre soft float lowering. From what I can see, in the beginning of ISelLowering code, the DAG will still reflect the original prototype. If I do a DAG.viewGraph() there in the debugger, it knows about the proper prototype (pre soft float lowering). It would have been cool to get the function class that corresponds to this call and get the arguments that way but I don't see how I can get it. Is looking at the DAG the only (or best) way to do find t...

...there some option when > > invoking the compiler (I've seen some -print-cfg and -dot-cfg options > > mentioned in some source files, but I can't find which tool supports > > them) > > > > This should help: > > http://llvm.org/docs/ProgrammersManual.html#ViewGraph > > > Hey Chris. Thanks for the prompt response. > That's what I was referring to before. If I'm getting this right, I > should do a debug build of LLVM and the run it from gdb? So say, I run > llvmc from gdb, pass on the code I want to compile and then what? Should &gt...

...tStr; } std::string getNodeLabel(Value *&Node, const MCDFGraph<MachineFunction *> &Graph) { if (isSimple()) return getSimpleNodeLabel(Node, Graph); else return getCompleteNodeLabel(Node, Graph); } }; *//Calls to ViewGraph and WriteGraph from the respective passes' runOnMachineFunction* ViewGraph(MCDFGraph<MachineFunction*>(&F), "Function:" + (F.getFunction())->getName()); WriteGraph(File, (MCDFGraph<MachineFunction*>)&F); The MachineInstrIterator.h is quite lengt...

...lt;DFG<Function*> > : public GraphTraits<Value*> { typedef inst_iterator nodes_iterator; static nodes_iterator nodes_begin(DFG<Function *> F) { return inst_begin(*F); } static nodes_iterator nodes_end(DFG<Function *> F) { return inst_end(*F); } }; ... ViewGraph(DFG<Function*>(F), "test"); Then you could implement a DOTGraphTraits for DFG<Function*>. > > 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...