Thanks @tqchen for comments. To elaborate more here, the support for Relay to ONNX serialization will help us to take advantage of hardware-specific optimizations supported by different compilers. The ONNX format is mostly adopted. If a particular compiler supports a specific format, support for it can also be added. Examples of other formats can be NNEF, PFA, TFLite etc.
Yes, there will be some use cases that will not be supported by ONNX and this will be true for other portable formats as well. But we can take advantage of Bring Your Own Codegen and Graph Partitioning feature. The model graph can be annotated and partitioned based on ops supported by ONNX runtime. For subgraphs annotated for ONNX, we serialize it to ONNX and then ONNX runtime should be able to run it. For the rest of the graph, we fallback to TVM runtime. This feature will add generic support for serializing the Relay graph to ONNX and can be used by the external codegen and runtimes. --- [Visit Topic](https://discuss.tvm.ai/t/rfc-relay-to-onnx/6101/4) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/65971c3cbdd70cc28fb72f2c2d4eacda4e57bc27d01fc6a6a04e5e19b8037c24).
