Lines Matching +full:node +full:- +full:version

2 How To Add A Constrained Floating-Point Intrinsic
20 Add SelectionDAG node types
23 Add the new STRICT version of the node type to the ISD::NodeType enum::
27 Strict version name must be a concatenation of prefix ``STRICT_`` and the name
28 of corresponding non-strict node name. For instance, strict version of the
29 node FADD must be STRICT_FADD.
52 -------------------------
57 STRICT_FP_ROUND. The new STRICT node will eventually be converted
58 to the matching non-STRICT node. For this reason it should have the same
59 operands and values as the non-STRICT version but should also use the chain.
60 This makes subsequent sharing of code for STRICT and non-STRICT code paths
65 Most of the STRICT nodes get legalized the same as their matching non-STRICT
66 counterparts. A new STRICT node with this property must get added to the
72 places where the non-STRICT counterpart is legalized and update as needed.
76 The code to do the conversion or mutation of the STRICT node to a non-STRICT
77 version of the node happens in SelectionDAG::mutateStrictFPToFP(). In most cases
85 Whether the mutation may happens or not, depends on how the new node has been