Lines Matching refs:Toy

8 abstraction; the Toy dialect that we have previously defined is one such
15 like Toy to get the information they need.
28 Our Toy IR currently operates on generic tensors, meaning that we don't know the
37 duplicates the called function and specializes it. The approach we take for Toy
43 Here we could write an inlining algorithm specifically designed for the Toy
48 do in Toy is to provide the [interfaces](../../Interfaces.md) for the inliner to
52 operations in the Toy dialect. This information is provided through a
58 /// This class defines the interface for handling inlining with Toy operations.
65   /// into the given call. For Toy this hook can simply return true, as the Toy
73   /// given region. For Toy this hook can simply return true, as all Toy
82   /// Toy, any function can be inlined, so we simply return true.
89   /// terminator that we have in the Toy dialect is the return
122 We then register our dialect interface directly on the Toy dialect, similarly to
185 Now that the inliner has been informed about the Toy dialect, we can add the
186 inliner pass to the pass manager for Toy:
219 to add a new operation to the Toy dialect, `ToyCastOp`(toy.cast), to represent
311 constraints of the operations within the Toy dialect, but this seems like a good
361 Now that the interface is defined, we can add it to the necessary Toy operations
381 At this point, each of the necessary Toy operations provide a mechanism by which
457 test/Examples/Toy/Ch4/codegen.toy -emit=mlir -opt`.
461 Toy operations.