All the items are merged as of today. As a result, this issue is closed. Thanks
everyone for pushing and landing this major effort.
--
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#i
Closed #7527.
--
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#event-5404079206
Thanks @junrushao1994.
--
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-909129132
Hey @manupa-arm, to clarify, Relay integration is probably not happening prior
to meta schedule, but along with meta schedule (see M4a of meta schedule
timeline). Right now we can use either #7987 or just handwrite TensorIR to play
with the scheduling/codegen code path
--
You are receiving thi
Ack, Many thanks for the info 🙂!
--
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-907200410
Hey @manupa-arm,
Don't worry. We will make TensorIR be an optional but not the default backend
of relay as our first step. There must be many works (including meta schedule
and some corner cases that meta schedule can not generate automatically) to do
before totally switching TE to TensorIR.
Hey @junrushao1994 ,
Thanks for the clarifications.
Since the relay integration is supposed to be happening prior to meta schedule
is being concluded, what would be the default 'schedule' (or maybe in the
context of TensorIR: default set of scheduling passes) used in a relay.build
flow ?
--
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 A
Ack. Thanks.
Out of curiosity for the planned relay integration,
* Will the integration be using #7987 ?
* 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?
* Will it include rewriting schedules in TOPI
Thanks, @manupa-arm.
Of course, we will! The ultimate goal of TensorIR is to replace the current TE
schedule.
Before integrating it to `relay`, we need to finish all of our M2 items (there
are only two left). Here are the following steps:
- TensorIR docs and tutorial
- Relay integration
- Met
Hi @junrushao1994 @Hzfengsy ,
Thanks for the effort that goes in here. Some of this scheduling primitives are
really useful that are not there in TE.
Will there be a task to integrate these scheduling primitives to be used by
main compilation flow? (i.e. relay.build) ?
--
You are receiving th
11 matches
Mail list logo
