Lines Matching full:operations

7 The Transform dialect uses the dialect extension mechanism to allow additional operations to be inj…
21   // dialect  definitions. List individual operations and dependent dialects
30   // the attributes or types used by transform operations. Do NOT declare as
35   // When transformations are applied, they may produce new operations from
37   // itself dependent on the dialects containing such new operations. To avoid
40   //   - dependent dialects, which are used by the transform operations, and
41   //   - generated dialects, which contain the entities (attributes, operations,
44   // In the following chapter, we will be add operations that generate function
45   // calls and structured control flow operations, so let's declare the
50   // Finally, we register the additional transform operations with the dialect.
57 The operations themselves can be defined using ODS, exactly in the same way as regular operations i…
79 …e must use Tablegen to generate the header and implementation of these operations. We can instruct…
122 …posed to be included into the declaration and definition of the transform operations, respectively.
143   // Finally, we register the additional transform operations with the dialect.
144   // List all  operations generated from ODS. This call will perform additional
145   // checks that the  operations implement the transform and memory effect
156 …gular operation in a dialect. Note that the Transform dialect requires operations to implement the…
177 …Generates a silenceable failure if the operand is associated with payload operations that are not …
180   // The arguments include the handle to the payload operations and the
233   // First, we need to obtain the list of payload operations that are associated
275 This is enough to define transform operations. The only remaining bit is providing the extension re…
294     // Since the %arg2 handle is associated with both elementwise operations,
307     // We can now fuse the other operations into the loop. Here, we fuse
308     // operations one-by-one. This requires the operation that is being fused
311     // a single handle to all operations and give it to
334     // operations such as loops, use tiling to size 1 to materialize the outer