@yelite It's a great RFC，and this is what we need right now. the requirements we need: 1) For compute fusion. With TE compute, it's easy to concate TE computes with producer-comsuer relation to get a fused compute. for example, conv + elemwise ops fusion. We should have similar function in TVM script. Which thread is related to this requirement? 2) For conditional lowering. We may have some attributtes in graph/relay level, which will further decide how to lowering into different tir. With old ir builder/TE compute, we can do that. F4 in this RFC will ensure this，correct？ 3) For reducing boilerplate code. F3 is a good idea. Another one is we define a tir function (with or without host python code), and we reuse it other place. We see this in F4 which foucus on conditional lowering, however I think we should define/declare it as standalone Fearture.
Looking forward to see this RFC in upstream! -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/79#issuecomment-1181184802 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/79/c1181184...@github.com>
