Thanks for your reply! @kevinthesun 

[quote="kevinthesun, post:9, topic:7872"]

Thank you for this proposal! This work does make scheduling much easier. I have 
a concern about using this way to write a tensor expression. It looks like more 
complicated than tvm.compute when defining matmul. We need to define some 
buffers and creating block with corresponding shape dimension. It would be 
helpful if you can add a conv2d example which can replace existing 
topi.nn.conv2d definition to better understand what developer would need to 
write.
[/quote]

In original te programming, we also have to declare buffers and create lambda 
expression with iter_vars having the correct shape dimension. If we take this 
additional info into account, TE programming is close to Hybrid Script's 
programming in complexity.

Currently, we can not replace existing topi operators, since they are 
represented by Stage/Op and optimized by te schedule, while Hybrid Script will 
be parsed into TIR directly.

[quote="kevinthesun, post:9, topic:7872"]
Another question is about representing generic programming style ops such as 
shape functions. Since these programs don’t fit into tvm scheduling, I assume 
it would still be more convenient to use existing te hybrid script to create 
these ops?
[/quote]

If we don't have to schedule the PrimFunc, we don't have to declare blocks in 
TIR. 
Actually, TE hybrid script is also a text representation of TIR to a large 
extent, with loop and condition statement directly representing the IR 
structure, using sugar like variable being translated to Array of size 1 to 
ease the format of Store&Load. At the moment, we haven't introduced sugars to 
simplify such Load&Store, but the rest writing are largely simlilar.





---
[Visit 
Topic](https://discuss.tvm.apache.org/t/rfc-tensorir-a-schedulable-ir-for-tvm/7872/10)
 to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.apache.org/email/unsubscribe/b56ad45dd9069fd09fb5ae1b434a3d4d598842a38b39e2b2aea236c55b1ccad3).

Reply via email to