@areusch: Forgot to answer your first question. Yes, for now, we like to generate external JSON files, only for the accelerator sub graph(s), in the BuildResult step so that we can pass them to our not-(yet-)in-TVM-general-flow, external-accelerator-specific compiler backend program to do further AOT for-inference-run optimization in order to generate more optimized ISA code to run inference for the accelerator sub graph(s). For the llvm sub graphs (let me use llvm here to distinguish them from those for-accelerator sub graphs), we will and do follow the TVM general flow to generate the .so lib files. When the Model Library format and flow become stable, plus, they can be specialized to include extra external accelerator and memory allocations & communications, we definitely like to see how we can advance the BYOC-Marvell flow to use them (with llvm .so lib files together).
-- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/48#issuecomment-1022618855 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/48/c1022618...@github.com>
