Hey @manupa-arm thanks for your interest! > Will the integration be using #7987 ?
Most of the operators are defined with the TE DSL in TOPI, so in these cases we will definitely use #7987, which converts TE compute dag to TensorIR. > If you guys have decided, please let us know what other the APIs (at least > initially) be used to create the high-level non scheduled Primfunc? Yep, we introduced a python-based text format (so it's the frontend for TensorIR DSL) as a convenient way to write scehduleable TensorIR. Our unittests contain a lot of examples of these: https://github.com/apache/tvm/blob/main/tests/python/unittest/test_tir_schedule_split_fuse.py#L29-L34. > Will it include rewriting schedules in TOPI? i.e. decoupling te.compute and > scheduling applied to TE graph as passes? Great question! While #7987 converts TE compute dag to TensorIR, we cannot reuse TOPI's schedule and AutoTVM schedule templates. However, as meta schedule is coming to the rescue, in most of the cases, schedule can be generated automatically with meta schedule. We are designing some APIs to allow customized schedule as well. Happy to discuss more if you are interested :-) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/tvm/issues/7527#issuecomment-907032840
