Lines Matching full:operations

1 # Chapter 4: Matching Payload with Transform Operations
7 that specific payload operations are identified by the caller when the transform
15 a subset of operations for _matching_ payload operations that need to be
18 _Match_ operations are simply transform operations with some additional
22 operation names or kinds of arguments. Using simple combinator operations, it
63 associations for operation handles. Instead, we can use match operations to
64 discover relevant operations in the payload IR. Match operations can be combined
65 with “regular” transform operations using, e.g., the
78     // Collect operations that match the criteria specified in named sequence.
130 `linalg.elemwise_binary` and `linalg.matmul` operations. In debug builds, the
133 will print the silenceable failure messages produced by the match operations
149 ## Matching Chains of Operations
151 The matcher above remains naive as it matches _all_ operations of the certain
152 kind under the payload root. These operations may or may not be related, and
154 function, if there are multiple groups of such operations, we wouldn’t be able
156 specific group of operations where a `matmul` operation produces a result that
165 // match and nested operations must succeed in order for a match to be deemed
191   // operations separately.
198 operations and will return the triple of _related_ operations rather than
199 operations in the order in which they are found. It can be exercised similarly
206   // Collect groups of operations that match the criteria specified in the
222 ## Defining Match Operations
224 The matcher of a chain of operations is correct in presence of other operations,
227 operand of elementwise operations is produced by another operation. The same
229 many binary operations are associative. Let us use this opportunity to introduce
232 other match operations. We also want it to return some of the state and the
235 Match operations are defined similarly to other transform operations, with the
259   // Match operations can be arbitrarily complex, e.g., containing regions.
269 It takes as argument the handle associated with the payload operations whose
275 `TransformOpInterface` and is easily composable with other transform operations.
278 operations. Match operations are expected to return a silenceable failure to
280 they have nested operations, they are expected to handle and, in most cases,
281 silence the silenceable failures produced when applying those operations. For
373 By convention, operations implementing `MatchOpInterface` must not modify
408   // operations nested in its region.
428   // operations separately.
442 In order to demonstrate that groups of operations are matched independently of
452 // @match_matmul_elemwise on each of the operations. If the named sequence
453 // succeeds, i.e., if none of the nested match (transform) operations
507 operations, many such match operations are readily available in the `structured`