This is a follow-up of https://github.com/apache/tvm/pull/9727 and
[RFC#63](https://github.com/apache/tvm-rfcs/pull/63). Currently buffer can be
implicitly declared and then used. The implicit behavior can be error prone and
makes analysis more difficult. This RFC introduces `DeclBuffer`, a new
@areusch and @MichaelJKlaiber, I agree with using [Target-registered
compilation flow
customization](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0010-target-registered-compiler-flow-customisation.md).
I am struggling to how to connect that with :
```
TVM_REGISTER_GLOBAL("relay.backend.con
@areusch and @manupa-arm :
For A2, we agree. [Target-registered compilation flow
customization](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0010-target-registered-compiler-flow-customisation.md)
is the way to go here.
CC: @cgerum @PaulPalomeroBernardo
--
Reply to this email directly
Thanks folks for discussions. Just want to chime in here. I think we all agree
that the development and upstreaming flow should closely follow the normal
process, which is A2 as being listed by @denise-k .
For emerging components being contributed to the community, it is certainly
helpful for
This is a global tracking issue for landing the initial PRs of **UMA**. The
original RFC can be found
[here](https://github.com/boschresearch/tvm-rfcs/blob/rfc_uma/rfcs/00xx_UMA_Unified_Modular_Accelerator_Interface.md).
Please feel free to bring in more questions to the corresponding thread.
T
> If I'm interpreting your message correctly, your concern is that Relax's
> current approach towards development does not yet utilize any of these task
> tracking mechanisms.
Apologies, I'll clarify, there is no need for Relax to use any of TVMs
development process, as it's an exploratory proj
