Lines Matching full:payload

11 transformed as payload IR, and to the IR guiding the transformation as
17 size) in the payload IR, applying loop tiling to those and only those
21 common case, the transform IR will be processed and applied to the payload IR by
41   * sets of operations in the payload IR;
43   * sets of values in the payload IR;
50 loops found in the payload IR that satisfy the condition, and `%2` correspond to
56 An operation handle such as `%0` may be associated with multiple payload
59 Similarly, a value handle such as `%3` may be associated with a set of payload
62 Transform IR ops support operand values that are mapped to multiple payload
78 Alternatively, parameters can associate with the payload IR where the specific
81 payload IR.  Note that it is generally discouraged to use parameters containing
95 handle type interface implementation may check whether all associated payload IR
98 associated payload IR values are block arguments or have a specific type, or a
102 operation. The conditions are verified when payload objects operations are first
112 execution time. This approach allows one to capture payload IR operation
136 payload IR contained in `payloadRoot`. The payload root operation will be
167     transformation on the payload IR.
170     the transform IR operation on the payload IR as well as on the mapping
171     between transform IR values and payload IR operations. See below for
192     mapping between transform IR values and payload IR operations.
200       entry, typically after a transformation that modifies the payload IR
204   * `PayloadIRResource` - side effect resource corresponding to the payload
207     - A `Read` effect from this resource means accessing the payload IR.
209     - A `Write` effect on this resource means mutating the payload IR. It is
214 with a list of payload IR operations. This corresponds to `Allocate` and
217 only inspect the payload IR to produce new handles are usually limited to
219 payload IR are thought to _consume_ the handles provided as operands, that
222 transform IR, this value is likely associated with payload IR operations
231 operation and applies to some user-specified payload IR scope, identified by
232 the payload IR op that contains the IR to transform. It is the
263 if they haven't yet modified the payload IR, i.e. when reporting a
267 payload IR targets for the following transformation may have a conceptual
269 execution model but results in handles associated with empty payload IR
274 The execution model of the Transform dialect allows a payload IR operation to be
275 associated with _multiple_ handles as well as nested payload IR operations to be
276 associated with different handles. Similarly, a payload IR value may be
278 operation consumes a handle, it usually indicates that the corresponding payload
280 that _may_ be pointing to an erased payload IR object are _invalidated_. The
284 of the payload IR objects associated with it remain live.
290     - operation handles associated with one of the payload operations that the
294       payload operations described above;
303     - operation handles associated with payload operations that produce as
307     - operation handles associated with payload operations _nested_ in the
308       payload operations described above;
310     - operation handles associated with payload operations (recursively)
323 to an object defined or contained in the payload IR subtree rooted at the
332 payload IR.
386 and operations in the payload IR, or the function that applies the
408 ops rather than having the methods directly act on the payload IR.