Thanks @tqchen @icemelon9 I'll change to use intrinsic and make it more general.
--
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/incubator-tvm/issues/4487#issuecomment-564298170
After one cycle of deprecation it is now time to start the removal of legacy
NNVM code. NNVM's existence in the repo is preventing some refactoring to occur
for @icemelon9's new dynamically sized kernel generation work.
I know we still have some external consumers of NNVM and we should be mindf
@FrozenGene, I'd like to try to implement this. I am thinking if I could
follow @Huyuwei proposal by doing this with backward compatible way.
The padding would accept 1 value, or 2 values, or 4 values ( 3 and 6 for coming
3d ops).
For 1 and 2 case, the existing logic would be kept, which woul
Yes. We should keep the backward compatibility.
--
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/incubator-tvm/issues/2682#issuecomment-564353521
Our rust code uses NNVM for testing and a usage document. They need to be
updated.
--
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/incubator-tvm/issues/4496#issuecomment-564358394
VTA's dependence on NNVM (#4419) has mostly been removed; documentation and CI
dockerfiles have to be updated to reflect this.
--
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/incubator-tvm/issues/44
