I've seen that current uTVM flow uses module.save(..) interface to save the "c" module prior to compiling it to the micro binary that is fed to the runtime. I was wondering if we use the BYOC on the flow and create our own external c-source module/function additionally to the single dso_module(c-source) created today, how would that fit in the flow ?
I assume that it could be another c source that could get linked in the same way ? Highly appreciate any ideas on it. Also, if so I was wondering what would be a better way to store the constant binary artifacts produced as part of the lowering of the external function, that are needed in the runtime ? (someway better than having them in source) cc: @areusch @weberlo @tqchen @grant-arm --- [Visit Topic](https://discuss.tvm.apache.org/t/external-modules-in-utvm/7993/1) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/a259733e2404ae259a1871d348606e36cda9b437df80ea9071793e53b15863f3).
