Lines Matching refs:TokenFactor
1726 /// it would induce a cycle) and whether we have a TokenFactor node sandwiched
1764 // If we have a TokenFactor, we handle it specially.
1765 if (User->getOpcode() != ISD::TokenFactor) {
1792 // If we found a TokenFactor, there are two cases to consider: first if the
1793 // TokenFactor is just hanging "below" the pattern we're matching (i.e. no
1795 // the TokenFactor can be sandwiched in between two chained nodes, like so:
1804 // [TokenFactor] [Op]
1811 // In this case, the TokenFactor becomes part of our match and we rewrite it
1812 // as a new TokenFactor.
1817 // If the uses of the TokenFactor are just already-selected nodes, ignore
1821 // If the uses of the TokenFactor lead to nodes that are not part of our
1829 // Okay, we know we're in the interesting interior case. The TokenFactor
1833 // inputs as inputs to the ultimate TokenFactor we create.
1847 /// induce cycles in the DAG) and if so, creating a TokenFactor node. that will
1853 // users of the chain result. This adds any TokenFactor nodes that are caught
1862 // Okay, we have walked all the matched nodes and collected TokenFactor nodes
1863 // that we are interested in. Form our input TokenFactor node.
1867 // the operands of the generated TokenFactor) if it's not an interior node.
1869 if (N->getOpcode() != ISD::TokenFactor) {
1892 return CurDAG->getNode(ISD::TokenFactor, SDLoc(ChainNodesMatched[0]),
2168 case ISD::TokenFactor:
