Displaying 8 results from an estimated 8 matches for "setsubgraphcolor".
2008 Oct 27
2
[LLVMdev] new warnings in r58273
llvm/llvm/lib/CodeGen/SelectionDAG/SelectionDAGPrinter.cpp: In member
function ‘void llvm::SelectionDAG::setSubgraphColor(llvm::SDNode*,
const char*)’:
llvm/llvm/lib/CodeGen/SelectionDAG/SelectionDAGPrinter.cpp:372:
warning: comparison with string literal results in unspecified behavior
llvm/llvm/lib/CodeGen/SelectionDAG/SelectionDAGPrinter.cpp:375:
warning: comparison with string literal results in unspecified...
2009 Jul 13
0
[LLVMdev] [PATCH] Support asm comment output
On Jul 13, 2009, at 10:02 AM, David Greene wrote:
>>> - Tag instructons with source line information (customers really
>>> want this).
>>
>> Right, that would be nice. This should be synthesizable from the
>> DebugLoc on the instruction in the asm printer, no need to
>> redundantly
>> encode it into the comment field.
>
> Except the DebugLoc
2008 Oct 03
1
[LLVMdev] Making Sense of ISel DAG Output
...ge graphs that LLVM
> doesn't yet have is the ability to display subsets of the graph.
> For example, take a node of interest and show just it and its
> operands and its users. Or maybe two or three or N levels of
> operands.
Yes, this would be helpful. I also looked at creating a setSubgraphColor
method that would color the node and its children. But there doesn't seem to
be a convenient way to traverse SelectionDAGs. It seems to be hard-coded by
tblgen.
-Dave
2008 Oct 27
0
[LLVMdev] new warnings in r58273
On Monday 27 October 2008 17:06, Mike Stump wrote:
> llvm/llvm/lib/CodeGen/SelectionDAG/SelectionDAGPrinter.cpp: In member
> function ‘void llvm::SelectionDAG::setSubgraphColor(llvm::SDNode*,
> const char*)’:
> llvm/llvm/lib/CodeGen/SelectionDAG/SelectionDAGPrinter.cpp:372:
> warning: comparison with string literal results in unspecified behavior
> llvm/llvm/lib/CodeGen/SelectionDAG/SelectionDAGPrinter.cpp:375:
> warning: comparison with string literal resu...
2009 Jul 13
2
[LLVMdev] [PATCH] Support asm comment output
On Monday 13 July 2009 11:40, Chris Lattner wrote:
> > I was attempting to reduce the number of files affected, but if you
> > want this change I'll go ahead and do it.
>
> Makes sense, thanks. Please do it as a separate patch from the other
> changes though since it will be large and mechanical.
Ok, no problem.
> > - Tag instructons with source line information
2009 Jul 13
5
[LLVMdev] [PATCH] Support asm comment output
...cate_load>>
// Emits: (MOV32rm:i32 addr:iPTR:$src)
PatternID = 1367;
// Pattern complexity = 19 cost = 1 size = 3
SDValue CPTmp01;
SDValue CPTmp11;
SDValue CPTmp21;
SDValue CPTmp31;
if (SelectAddr(N, N1, CPTmp01, CPTmp11, CPTmp21, CPTmp31)) {
CurDAG->setSubgraphColor(N.getNode(), "red");
SDNode *Result = Emit_125(N, X86::MOV32rm, MVT::i32, CPTmp01, CPTmp11,
CPTmp21, CPTmp31, PatternID);
if(Result) {
CurDAG->setSubgraphColor(Result, "yellow");
CurDAG->setSubgraphColor(Result, "black");
}...
2008 Oct 03
0
[LLVMdev] Making Sense of ISel DAG Output
On Oct 2, 2008, at 2:15 PM, David Greene wrote:
> On Thursday 02 October 2008 15:37, Dan Gohman wrote:
>>
>> Also, you can call viewGraph() from within a debugger, to view
>> the graph at arbitrary point in the middle of the selection
>> process. You can can even put a breakpoint on the Select
>> function and view the graph as each individual instruction is
2008 Oct 02
2
[LLVMdev] Making Sense of ISel DAG Output
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.
> Also,