# \[RFC\] Standalone Code Generation and C Runtime for STM32 bare-metal devices

**URL:** <https://discuss.tvm.apache.org/t/rfc-standalone-code-generation-and-c-runtime-for-stm32-bare-metal-devices/9562>\
**Category:** Development\
**Created:** [March 29, 2021, 4:00pm UTC](https://discuss.tvm.apache.org/t/rfc-standalone-code-generation-and-c-runtime-for-stm32-bare-metal-devices/9562 "2021-03-29T16:00:24Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![giuseros](https://discuss.tvm.apache.org/user_avatar/discuss.tvm.apache.org/giuseros/32/803_2.png) [@giuseros](https://discuss.tvm.apache.org/u/giuseros)\
**Post date:** [April 1, 2021, 4:38pm UTC](https://discuss.tvm.apache.org/t/rfc-standalone-code-generation-and-c-runtime-for-stm32-bare-metal-devices/9562/7 "2021-04-01T16:38:35Z")

</div>

Hi all,

I just published the AOT PR upstream: [[AOT] Introducing AOT in TVM by giuseros · Pull Request #7785 · apache/tvm · GitHub](https://github.com/apache/tvm/pull/7785).

It has some conflicts probably due to the `GraphExecutor` refactoring, and I will fix that soon. I wanted just to let you guys start to have a look

@stoa I am wondering how much of your work can use the AOT code generation in that PR.

Thanks, Giuseppe

---

_[View the full topic](https://discuss.tvm.apache.org/t/rfc-standalone-code-generation-and-c-runtime-for-stm32-bare-metal-devices/9562)._
