Merged #33 into main.
--
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-vta/pull/33#event-5184321050
@vegaluisjose @liangfu can you take a look? thanks!
--
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-vta/pull/33#issuecomment-902230052
Thank you @ekiwi - glad to see your changes use the latest stable release.
--
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-vta/pull/33#issuecomment-902229418
If there is not other objections, this will be merged on monday.
--
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/6#issuecomment-902192178
IMHO, the docs should serve for two major purposes:
1. For pure users who don't care how TVM is implemented but just want to
achieve high performance, we need to let them hands on as convenient as
possible.
2. For new developers who want to improve something with TVM, we need to let
them know
This PR ports the chisel hardware to use the latest stable release.
It also cleans up any deprecation warnings.
You can view, comment on, or merge this pull request online at:
https://github.com/apache/tvm-vta/pull/33
-- Commit Summary --
* modernize build.sbt
* fix some imports
* ignore
Thanks, @hogepodge. It's a good opportunity for us to enhance TVM documentation
and tutorials together. I want to share some of my thoughts on it.
## A Separated Developer Documentation
Users(who will use TVM as a tool to compile models on supported models and
backends and won't change much of
Thanks @hogepodge for the RFC. It would be great for us as a community to
converge on a documentation system that we can all collaborate together.
Based on the current proposals, I find that it might be helpful to dissect the
possible choices here to facilitate the discussion(since we might wa
I would prefer L2 in terms of more precise section titles. Sometimes it is
really hard to distinguish "User Guide" and "Developer Guide", and L2 replaces
them with more explicit terms "Tutorials by example", "Architectural guide by
each component of TVM system". The only thing missing here is
