This is to try to fix the problem described here :http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20150622/284139.html
Details
Diff Detail
Event Timeline
lib/CodeGen/SelectionDAG/DAGCombiner.cpp | ||
---|---|---|
14022 | Can you explain exactly what situation your trying to prevent and why it is bad? I don't understand the problem from the referenced mailing-list message because everything there looks legal. |
lib/CodeGen/SelectionDAG/DAGCombiner.cpp | ||
---|---|---|
14022 | My problem/question is is it allowed for a node using the value out of a CopyFromReg to be on the same chain as the CopyFromReg itself? I'm not seeing it right now with just the isAlias patch, but it looked something like PtrVal, Chain0 = CopyFromReg EntryToken ... It's possible I had something else broken in my tree that I don't remember. I'll see if I can run into this again with some of the other patches I'm working on. |
lib/CodeGen/SelectionDAG/DAGCombiner.cpp | ||
---|---|---|
14022 | Yes, I believe this is legal. Data dependencies do not need to be redundantly encoded as chain dependencies also. |
Can you explain exactly what situation your trying to prevent and why it is bad? I don't understand the problem from the referenced mailing-list message because everything there looks legal.