Displaying 4 results from an estimated 4 matches for "setgraphcolor".
2008 Oct 02
0
[LLVMdev] Making Sense of ISel DAG Output
...nd view the graph as each individual instruction is
selected.
It can get hairy with really large graphs, but if you're trying
to understand instruction selection, it's often possible to reduce
the testcases to a readable scale while still including the
interesting parts. SelectionDAG's setGraphColor method can also
help when graphs get large.
And FWIW, there are some significant improvements in the
viewGraph() output in TOT :-).
Dan
2008 Oct 02
2
[LLVMdev] Making Sense of ISel DAG Output
...ich Select function are you referring to?
> It can get hairy with really large graphs, but if you're trying
> to understand instruction selection, it's often possible to reduce
> the testcases to a readable scale while still including the
> interesting parts. SelectionDAG's setGraphColor method can also
> help when graphs get large.
Unfortunately, the testcase is about as simple as it can get: a loop with a
gather, a multiply and a store. Maybe I can hand-whittle some IR.
> And FWIW, there are some significant improvements in the
> viewGraph() output in TOT :-).
Yeah,...
2008 Oct 02
4
[LLVMdev] Making Sense of ISel DAG Output
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 =
2008 Oct 03
0
[LLVMdev] Making Sense of ISel DAG Output
...the x86 target.
>
>
>> It can get hairy with really large graphs, but if you're trying
>> to understand instruction selection, it's often possible to reduce
>> the testcases to a readable scale while still including the
>> interesting parts. SelectionDAG's setGraphColor method can also
>> help when graphs get large.
>
> Unfortunately, the testcase is about as simple as it can get: a loop
> with a
> gather, a multiply and a store. Maybe I can hand-whittle some IR.
Another trick is to place an abort() call somewhere in codegen
such that it will...