@junrushao1994 does this mean that 0.8 will go out with half finished
implementations for things, such as library integrations (i.e. CMSIS-NN) and
tvmc arguments (tvmc is not yet stable as there's breaking changes incoming)?
If the process is just to take `main` and tag it, can we rapidly move t
@mehrdadh thanks for the review!
Yes, if a Project API method implementation is absent a `TypeError` will be
raised at the server side because the abstract method is not implemented when
the Handler class is derived. Also as per
https://github.com/apache/tvm-rfcs/blame/main/rfcs/0008-microtvm-p
For the proposed BYOC flow (i.e.,
`MergeAndAnnotate`/`AnnotateSEScopes`/`PlanDevices`/`PartitionBySEScope`), it
doesn't clear to me that whether the developer programming model will change or
not. Specifically, could we still use the current approaches (i.e., op-based
annotation and pattern-bas
I'd suggest adding the `BufferTransform` data structure here which will be very
helpful to other audience.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/39#issuecomment-955098088
Hi, @junrushao1994
I think we could add paddlepaddle frontend as a new feature in the release note
of v0.8
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm/issues/8976#issuecomment-955121366
