Lines Matching full:strict

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
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.
73 Be careful of the chain since STRICT nodes use it but their counterparts
76 The code to do the conversion or mutation of the STRICT node to a non-STRICT
86 registered in TargetLoweringBase::initActions(). By default all strict nodes are