Displaying 4 results from an estimated 4 matches for "isqu".
Did you mean:
isql
2008 Oct 07
2
[LLVMdev] Making Sense of ISel DAG Output
...a
machine-dependent one (the SHUFPD).
When we pop back out to SelectRoot we run into this code:
if (ResNode != Node) {
if (ResNode) {
ReplaceUses(Node, ResNode);
}
if (Node->use_empty()) { // Don't delete EntryToken, etc.
ISelQueueUpdater ISQU(ISelQueue);
CurDAG->RemoveDeadNode(Node, &ISQU);
UpdateQueue(ISQU);
}
}
Since we did an in-placement replacement the first test fails and we don't
call ReplaceUses. I think this is correct EXCEPT that now we have orphaned
machine-independent loadf64...
2008 Oct 07
0
[LLVMdev] Making Sense of ISel DAG Output
...).
>
> When we pop back out to SelectRoot we run into this code:
>
> if (ResNode != Node) {
> if (ResNode) {
> ReplaceUses(Node, ResNode);
> }
> if (Node->use_empty()) { // Don't delete EntryToken, etc.
> ISelQueueUpdater ISQU(ISelQueue);
> CurDAG->RemoveDeadNode(Node, &ISQU);
> UpdateQueue(ISQU);
> }
> }
>
> Since we did an in-placement replacement the first test fails and we
> don't
> call ReplaceUses. I think this is correct EXCEPT that now we have...
2008 Oct 03
0
[LLVMdev] Making Sense of ISel DAG Output
On Fri, October 3, 2008 9:10 am, David Greene wrote:
> On Thursday 02 October 2008 19:32, Dan Gohman wrote:
>
>> Looking at your dump() output above, it looks like the pre-selection
>> loads have multiple uses, so even though you've managed to match a
>> larger pattern that incorporates them, they still need to exist to
>> satisfy some other users.
>
> Yes,
2008 Oct 03
3
[LLVMdev] Making Sense of ISel DAG Output
On Thursday 02 October 2008 19:32, Dan Gohman wrote:
> Looking at your dump() output above, it looks like the pre-selection
> loads have multiple uses, so even though you've managed to match a
> larger pattern that incorporates them, they still need to exist to
> satisfy some other users.
Yes, I looked at that too. It looks like these other uses end up being
chains to