[GitHub] [tvm-rfcs] masahi commented on pull request #89: [RFC] Relax Upstreaming

[GitBox <gi...@apache.org>]

masahi commented on PR #89:
URL: https://github.com/apache/tvm-rfcs/pull/89#issuecomment-1223774454

   @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 of work between Relay / Relax. We have many Relay passes that work all right and for which it doesn't make a lot of sense to reimplement in Relax. 
   
   But if Relax is supposed to be complementary to Relay, why do we keep calling it Relax, as "Relay Next"? "Relay Next" strongly suggests that Relax is something that is going to replace Relay, like we did for nnvm. I'm still not entirely clear if the plan is to eventually duplicate Relay, or Relay and Relax are going to coexist for foreseeable future.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@tvm.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org