-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DEV] TVM v0.7 Roadmap #4845
Comments
We will have a good support for pytorch including dynamic and quantized models. I have a series of PRs coming. |
Could you also add support for intel graphics as well. it seems it is not supported at the moment! |
External codegen integration with uTVM is highly interesting for us at CEVA. |
Is there any plan to integrate TVM as a dialect into MLIR? |
@yangjunpro Perhaps it worth to start a new thread in the discuss forum to discuss MLIR related topics. We certainly would love some proposals about interpolation between MLIR and TVM. |
I wonder is there any active effort working on the feature "Auto tensorization", and I'm interested in contributing. |
@liangfu auto tensorization depends on on the new IR update, we will send out specific guidelines after we finish the IR refactoring |
I am currently working on some end-to-end model stuff, and Relay's optimization pass are too slow. Any plans on improving the compilation speed? |
Can you identify why they are slow? For example switching some passes to the new iterative graph visitor might improve speed quite a bit. In previous profiling attempts I have found a significant amount of time is spent allocating, having a pooling allocator can often improve speeds quite a bit. |
I'd like to propose creating Relay |
re relay c_api, there is no need to do so, as all the relay functions are exposed through the PackedFunc FFI. So all the features of relay can already be accessed through the tvm's C API. |
What is the expected time of release for this release? what are the chances of it happening in May? |
Due to recent situation and the current progress, we might expect a bit of delay in the release to June/July -- we expect the unified IR refactor to land by then. We will do our best to keep the timeframe. |
Including more operator should be scheduled as least for one frontend? Onnx or tensorflow or mxnet etc, it will be great if 'ONE' frontend is widely supported!! |
We will have general support for TensorFlow control flow and tensor array, which allows parsing for TensorFlow object detection models |
Please see #6421 for release plan |
"Which are summarized summarized from the forum discussion." double summarized may be a small mistakes. |
v0.8 cycle tracking issue is created #7434 |
This roadmap for TVM v0.7. TVM is a community-driven project and we love your feedback and proposals on where we should be heading. Please open up discussion in the discussion forum as well as bring RFCs.
In the 0.7 cycle, we are going to focus on the following four areas. Which are summarized from the forum discussion.
We also welcome contributions along all the other areas, including more operator and model coverages, and they will be added to this list gradually. Please reply to this thread about what you would like to volunteer to work on.
We will aim to cut a release in about three months timeframe(around April, May)
Core Infra
Usability
Backend and runtime
Automation
The text was updated successfully, but these errors were encountered: