Good questions!
-
As for as we know, we would like to let users use TensorIR schedule rather than TE schedule one we fully upstream the TensorIR. For three reasons:
- Just as you have mentioned, TE is a fronted wrapper, and it directly generates TIR with blocks. Somehow, TE is more like a sugar to define TIR.
- Most of the schedules and primitives in TensorIR are very similar to those in TE. The cost of learning TensorIR schedule is extremely low (maybe just one day).
- All primitives are based on the block (no stage concept in TensorIR schedule). It’s hard to keep the TE schedule with block
-
Dynamic shapes are not supported now. However, thanks to our de-coupled primitives, it’s ok to support later.