TVM and MXNET share common dependencies bundled in their respective 3rdparty directories, and it is common to import both tvm
and mxnet
in the same projects, such as in this tutorial from_mxnet.py
Previously I encountered incompatibility issues after trying to pull and build the latest from tvm
and mxnet
and then use them in the same script. It was some time ago, but I believe it was related to differences in dlpack.h.
- mxnet/3rdparty/dlpack/include/dlpack/dlpack.h
- mxnet/3rdparty/tvm/3rdparty/dlpack/include/dlpack/dlpack.h
I have been using the commit number of mxnet/3rdparty/tvm
as a tested and compatible version indicator, however, I recently encountered a TVM issue that has been fixed in a newer version than the submodule pointer maintained in MXNET, and I was unclear on what the best update policy was in this scenario.
Are the compatible versions of MXNET and TVM documented, or is there a heuristic that might server to indicate whether or not two versions of MXNET and TVM are expected to work together? (The previous issue didn’t show up until runtime tests with the TVM tutorials.) Do people typically use the latest TVM and MXNET versions together without issue?