Name |
Last commit
|
Last update |
---|---|---|
.. | ||
README.md | ||
minimal_vector.h | ||
utvm_graph_runtime.cc | ||
utvm_graph_runtime.h | ||
utvm_runtime.cc | ||
utvm_runtime_api.cc | ||
utvm_runtime_api.h |
This is an alternative implementation of a subset of the TVM runtime API (and graph runtime) that focuses entirely on reducing code size, at the expense of functionality (no tvm.extern(..) calls via PackedFunc, CPU only, etc). It might be worth incrementally expanding the surface area if there's interest. The motivation for this work was seeing what the minimal useful subset of the TVM runtime is. This is relevant for e.g. super code-size constrained applications in e.g. embedded/mobile. The current runtime is more like O(100KiB) or so, so this might be compelling for some users. The smaller surface area for auditing might make this relevant for https://github.com/dmlc/tvm/issues/3159, or the usecases I was thinking about in https://github.com/dmlc/tvm/issues/2523#issuecomment-459165815 re: the Rust runtime. The symbols in the tvm::minimalruntime space (i.e. excluding std:: and picojson::) are about 5KiB, so I think there's a bunch of room here (i.e. we could replace picojson:: with [`jsmn`](https://zserge.com/jsmn.html) or something, and we could replace more of the `std::unordered_map` usage, etc with custom primitives as well (similar to the `DynArray`).
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
README.md | Loading commit data... | |
minimal_vector.h | Loading commit data... | |
utvm_graph_runtime.cc | Loading commit data... | |
utvm_graph_runtime.h | Loading commit data... | |
utvm_runtime.cc | Loading commit data... | |
utvm_runtime_api.cc | Loading commit data... | |
utvm_runtime_api.h | Loading commit data... |