areusch commented on pull request #7742:
URL: https://github.com/apache/tvm/pull/7742#issuecomment-918218038
@stoa and i discussed at length and are comfortable moving forward with
merging this. there will be two phases to the STM32 integration:
phase 1: merge the custom codegen and runtime implemented here
--- µTVM embedded C API reaches feature parity with STM32 API --
phase 2: re-implement the STM32 APIs as thin wrappers around µTVM embedded
C API. as this simplifies the STM32 codegen, consider removing it or moving it
into a Project API implementation.
- in general TVM prefers to have a singular runtime choice (we currently
have two: C++ for linux-like systems and C for bare-metal). in this case we are
okay merging STM32 support given that the TVM embedded C API is actively being
developed to feature parity with the STM32 API, the STM32 runtime component is
minimal, and having STM32 support in the codebase serves as a second point of
reference in designing middle compiler functionality to support a robust
embedded C API.
- target-wise: we can support dedicated stm32 targets through e.g.
`tvm.target.micro(board="stm32f746zg_disco")`
- test-wise: we can unit test the code-generator and runtimes as needed and
checkin a basic x86-based integration test. hardware-in-the-loop testing will
be addressed as µTVM begins to consider how to tackle this as a community.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
