Thanks everyone for the feedback. One thing that we seem to agree on is that
there is a strong need to support symbolic shape use cases for TVM, as
represented by many of the folks who chimed into this thread.
Hopefully, we all agree that there is a strong need to support robust and
high-qualit
As an individual Relax contributor from UCSD, I don’t feel our community has
created an environment that welcomes new contributors and new contributions.
I am happy to see different opinions in the discussion, but it's really
shocking and disappointing that we are afraid of moving forward even w
Merged #12898 into main.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/pull/12898#event-7520335399
You are receiving this because you are subscribed to this thread.
Message ID:
### This issue is to track progress for [Issue Triage
RFC](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0093_Issue_Triage.md).
This issue has these tasks:
* [x] Create labels described in the RFC.
* [ ] Modify ISSUE_TEMPLATES to remove Update CI Docker Image issue template
and add `need
Thanks for the discussion so far! Wearing Apache TVM hat, I would love to see
our community making progress to satisfy broader community and work with the
trend of deep learning compilation, rather than being gridlocked by a single
party of interest.
--
Reply to this email directly or view it
> @Mousius In this case, @YuchenJin 's reply clearly articulated that there is
> a close co-design of these factors, and changing to adopt dynamic alone would
> imply a one-step jump to relax -- which is not incremental. The data
> structure change would come with a set of supporting infra and c
@Mousius In this case, @YuchenJin 's reply clearly articulated that there is a
close co-design of these factors, and changing to adopt dynamic alone would
imply a one-step jump to relax -- which is not incremental. The data structure
change would come with a set of supporting infra and co-desig
