@ajtulloch Awesome work on this! We'll need a runtime for uTVM when we want to try self-hosted models, so the timing on this is great.
My general understanding is that it's much more common for bare-metal devices to support C, so it'd be interesting to see if we could incrementally whittle this down to pure C, like @mshawcroft said. Even if not, this would be a nice bonus for users targeting devices that *do* have C++ support. If we want to merge this into the µTVM namespace, `src/runtime/micro/standalone` seems fine. But since this is code that would be loaded onto the _device_, we could also put it in `src/runtime/micro/device/standalone`. Then we could move the current runtime in `device` into its own subfolder `device/host_driven` (or we could name it something else). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/dmlc/tvm/pull/3567#issuecomment-513428290
