Re: [apache/tvm-rfcs] [RFC] Add NNEF frontend (PR #108)

2024-05-09 Thread Viktor Gyenes
Great, thank you! -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/108#issuecomment-2102803235 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/tvm-rfcs] [RFC] Add NNEF frontend (PR #108)

2024-05-09 Thread Tianqi Chen
Leaving it open for another week in case others want to chime in, otherwise LGTM -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/108#issuecomment-2102706022 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/tvm-rfcs] [RFC] Add NNEF frontend (PR #108)

2024-05-09 Thread Viktor Gyenes
Thanks for the info about the schedules and differences, it makes sense. As for moving on, what would be the next step now? Do you need any other info from us for reviewing? -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/108#issuecomment-2102668139

Re: [apache/tvm-rfcs] [RFC] Add NNEF frontend (PR #108)

2024-05-09 Thread Tianqi Chen
I think the main reason here was relay default incorporate autotuning by default, while Relax dos not. The main rationale as of now is we would like to choose to decouple metaschedule tuning from the flow (as tuning is usually slower). That does not mean metaschedule cannot be applied, we do