Re: [apache/tvm-rfcs] [RFC] Relax Upstreaming (PR #89)

2022-08-23 Thread masahi
@YuchenJin > Relax can be viewed as complementary to Relay. Relay focuses on high-level op > transformations, while the current Relax passes focus on TIR-graph > co-transformations that can enable flexible fusion and layout rewrite, which > is hard to achieve in Relay. I like this separation

Re: [apache/tvm-rfcs] [RFC] Relax Upstreaming (PR #89)

2022-08-23 Thread Tianqi Chen
Thank you, everyone, for the discussions here. Let us take a step back and look at the non-technical parts of the conversation. A lot of our discussions come from two goals: G0: Maintaining a stable evolution solution for some of our common use-cases G1: Welcome new improvements, land our techni

Re: [apache/tvm-rfcs] [RFC] Add Commit Message Guideline (PR #88)

2022-08-23 Thread Leandro Nunes
@areusch can you have a final look and merge if you're happy, before creating the `[VOTE]` thread you mentioned? -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/88#issuecomment-1224165355 You are receiving this because you are subscribed to this thre

Re: [apache/tvm-rfcs] [RFC] Relax Upstreaming (PR #89)

2022-08-23 Thread Steven S. Lyubomirsky
On the point about potentially incorporating symbolic shapes into Relay, I would like to hear more detail about how it can be done with Relay's system of accumulating type constraints and solving them simultaneously. If we were to handle dynamic shapes in Relay, we would need to define semantics