Lines Matching refs:constraints

35 about each op, including its constraints, custom assembly form, etc. This
91     and constraints of the operation, including whether the operation has side
97     constraints over operands or results. A notable subclass hierarchy is
98     `Type`, which stands for constraints for common C++ types.
100     constraints over attributes. A notable subclass hierarchy is `Attr`, which
101     stands for constraints for attributes whose values are of common types.
201 `AttrConstraint` class hierarchy. See [Constraints](#constraints) for more
216 - provide a handle to reference for other places like constraints.
277 constraints on attributes beyond the ones brought by value types. You can use
278 `Confined` to compose complex constraints out of more primitive ones. For
282 Right now, the following primitive constraints are supported:
295 TODO: Design and implement more primitive constraints
351 ### Operation traits and constraints
357 and constraints involving multiple operands/attributes/results are provided as
359 the `OpTrait` class. See [Constraints](#constraints) for more information.
564 [constraints](#constraints) specified on various entities of the op. To perform
574 verification constraints. For verificaiton which needs to access the nested
656     -   The constraints on `inputs` and `results` are the same as the `input` of
967 via type constraints or other information available. In these cases, the type of
972 Some type constraints may only have one representation, allowing for them to be
979 There are many operations that have known type equality constraints registered
982 these equal constraints to discern the types of missing variables. The currently
1096 constraints. So both the operation definition and rewrite rules specification
1097 significantly involve writing constraints. We have the `Constraint` class in
1098 [`OpBase.td`][OpBase] as the common base class for all constraints.
1118 To help modelling constraints of common types, a set of `TypeConstraint`s are
1120 constraints of being a float, `TensorOf<[F32]>` for the constraints of being a
1124 constraints of common attribute kinds. They are the `Attr` subclass hierarchy.
1125 It includes `F32Attr` for the constraints of being a float attribute,
1126 `F32ArrayAttr` for the constraints of being a float array attribute, and so on.
1132 results. These constraints should be specified as the `Op` class template
1134 [Operation traits and constraints](#operation-traits-and-constraints).
1136 Multi-entity constraints are modeled as `PredOpTrait` (a subclass of `OpTrait`)
1143 commutative or not, whether is a terminator, etc. These constraints should be
1145 [Operation traits and constraints](#operation-traits-and-constraints).
1155 for composing constraints. The predicate for a constraint is typically built up
1184     replaced by `$attr`. For type constraints, it's a little bit special since
1185     we want the constraints on each type definition reads naturally and we want
1186     to attach type constraints directly to an operand/result, `$_self` will be
1219 TODO: Build up a library of reusable primitive constraints
1261 fine-grained constraints. For example, `StrAttr` directly maps to `StringAttr`;
1280     [further constraints](#confining-attributes).
1545 this means specifying traits, constraints and shape inference information in a
1579 *   The op's operand/return type constraints are modelled along with the op in