Thanks for the note.
As of now indeed relax is focused on non-MCU usecases. If there is some interest in doing embedded, it is still a good usecase. In the meantime, we also indeed would like to move away from monothlic piece in relay, where the usecase of multiple backends are intermixed together, ending making the core compiler less maintainable (which we don't want to end up with). The core piece of main pipeline now focuses on the new FFI mechanism that may should work for most mobile-level systems, but indeed ffi call for each op may not work for MCU level. However, diverging too much from the FFI can also cause issues, since the standalone unpacked api path can be brittle, because that afterall is not as well specified as the overall ffi abi. Just to note on the possible technical direction here : Technically i think likely what is needed is to try to get something aggressively inlined via the **partial graph AOT** as noted in this post https://discuss.tvm.apache.org/t/unified-python-first-compilation-flow-through-tvm-compile/18096 that means each individual tir fucntion get inlined and no longer needs to deal with the unpacked api issue. The interface still go with the packed API, but likely that is only single cost that can be paid, and with smart enough compiler and LTO that might get eliminated. Or take that AOT-fused relax graph fusion and take that into downstream that have good defined runtime. The key philosophy of relax is to enable out of tree deployment and customization so such pipelines can be created on top and perhaps not have to be in-tree initially, so starting something that relax pipeline outputs, and bringing into something could be a good starting point. --- [Visit Topic](https://discuss.tvm.apache.org/t/seeking-community-input-embedded-device-support-in-relax/18664/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/57978326fe8459ccce2ab7fca09ab09e0c45255370db7cb2b096468e5be93f39).
