-
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
[RFC][RELEASE] Apache TVM 0.6.0 Release Candidate (verifying, feedback, etc.) #4406
Comments
one typo... [RUTNIME] -> [RUNTIME] |
@FrozenGene Thanks. Fixed just now. Also we fixed some license problem per IPMC's comments. RC1: https://github.com/apache/incubator-tvm/releases/tag/0.6.0.rc1 |
we just moved the main website to https://tvm.apache.org/, might be worth cherry pick #4429 |
@tqchen sounds good. |
reported by @tmoreau89 and @liangfu There is a broken tutorial https://github.com/apache/incubator-tvm/blob/master/vta/tutorials/frontend/deploy_vision_on_vta.py which was caused by quantization changes that need to be fixed. Originally the quantize pass won't produce multiply if the scale is power2, and it is a hard requirement for VTA because vta does not have multiplier. seems the change #4295 allows creation of model with mul. @vinx13 would be great if you can help look into the problem. |
Fixed by #4433 |
I have made another RC per IPMC's comments and includes the bug fix. |
voting thread #4443 |
Dear Community,
This is an RFC for verifying whether v0.6.0.rc2 is good to go. The release candidate (release note, artifact and source code) can be find here
This is not an official vote. Please help us verifying,
For the vote afterwards, we propose to allow vote via github issue, which will be synced to @dev and back. See historical community vote on this thread dev@ thread: tvm apache community plan github thread: tvm apache community plan
We do encourage people also subscribe email list for tvm developers by sending email to [email protected]
@markusweimer @sscdotopen @tqchen
The text was updated successfully, but these errors were encountered: