So generally BYOC caters to two types of use cases that are mostly to handle accelerators and optimized operator libraries (e.g., Arm Compute Library, DNNL). I think in the world of micro, both of these should be invoked in the target_host via Driver/Runtime API component. i.e., even though there are object format that target_host could not execute, they might not be able to run on its own and would rely on the target_host to run some Driver/Runtime API to initialize and execute. I believe this bit of the code could be "c" or "o" with artifacts builtin into the runtime.Module.
I think only exception for this usecase is where we would have an packed function directly stored in an accelerator memory space that can support execution of standard procedure calls in its own binary format. Do you have a such a usecase in mind ? Nonetheless, even in that case I think the categorization should be done on artifact format rather than the codegen -- therefore we might as well use type_key for the folder structure? --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-tvm-model-library-format/9121/4) 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/00c1f9a7abef350eb0454ed2f2ce39da09018d4255a71802d92e27f6442c3c62).
