Thanks for the RFC! While I'm not familiar with the current RISC-V applications, I'm carious about the purpose of running Spike simulator and what would be the usual next step after it.
I also have some questions/thoughts about the implementation. In general I'm thinking if it would be better to integrate this flow via BYOC to provide more flexibility and opportunities for future hereogeneous execution. 1. I suppose Spike is a general processor, meaning that it is supposed to be executing any operators. 2. You mentioned to use LLVM as the backend. How does this LLVM backend overlap to the current TVM LLVM backend? Will you reuse most of it, or you almost build another backend using LLVM? 3. I didn't quite get the point of "since Spike doesn’t support parallel computing, we use an empty schedule for `schedule_injective()` , except for Ops that gonna be vectorized". Does that mean you still have schedules for the ops that can be vectorized? If so, do we need someone to write schedules for RISC-V P on Spike in TOPI? 4. In terms of the runtime, currently TVM graph runtime includes several modules, such as metadata module and external runtime modules (for the case of BYOC). Where would your custom runtime be? cc @zhiics --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-enable-tvm-qnn-on-risc-v-with-subword-simd-computation/7967/2) 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/636db6c8e192805911e59d7f786541f4e675829888c7c5df13914581b9c5bbf3).
