> We are getting confused with the difference between a stable architecture
> (components that interact with each other), with API, which is the specific
> function calls and classes design to make something work. What I'm arguing is
> that we should prioritise evolving our existing components e
+1 for this proposal
This will allow the project and community to move fast given the nature of the
space that the project is in.
Very clear description on what the expectation from the community and the
project.
NOTE: I saw a comment about having "value in having a stable architecture with
a
Hi @tqchen ,
While working on the solution, I see two more problems that I'd like to discuss
here:
1. No Control over flattening of buffers: If a buffer is flattened via
`FlattenLowAxisSepDimensions` , then it shouldn't be flattened via TIR passes
like `FlattenBuffer` or `FlattenStorage`. Is
+1 given the fast moving nature of this space, I'm in favor of this change and
I believe this will allow us adapt fast. Current RFC text seems clear to me.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/102#issuecomment-1671695963
You are receiving
