Merged #100 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/100#event-9050809705
You are receiving this because you are subscribed to this thread.
Message ID:
Thanks @yzh119. This RFC looks good to me. Looking forward to the 100th RFC
being merged :)
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/100#issuecomment-1514009320
You are receiving this because you are subscribed to this thread.
Message ID:
Hi @Lunderberg , I've changed the naming of some terms to avoid confusion,
don't hestitate to let me know if you have other concerns!
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/100#issuecomment-1513953529
You are receiving this because you are s
Hi @Lunderberg , thanks for your suggestions.
I think one point I need to emphasize is that the three constructs **Axes**,
**Sparse Buffers**, **Sparse Iterations** are new data structures and do not
change existing `block`/`buffer` data structures.
The expressions written under the body of **S
This RFC proposes a plan for integrating SparseTIR as a new dialect into TVM.
-
[rendered](https://github.com/yzh119/tvm-rfcs/blob/main/rfcs/0100-sparestir-dialect.md)
- [discussion
thread](https://discuss.tvm.apache.org/t/rfc-sparsetir-as-a-new-dialect-in-tvm/14645)
You can view, comment on, or
