# Implementing AOT in TVM

**URL:** <https://discuss.tvm.apache.org/t/implementing-aot-in-tvm/9206>\
**Category:** RFC\
**Created:** [February 23, 2021, 10:54pm UTC](https://discuss.tvm.apache.org/t/implementing-aot-in-tvm/9206 "2021-02-23T22:54:07Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![kparzysz](https://discuss.tvm.apache.org/user_avatar/discuss.tvm.apache.org/kparzysz/32/252_2.png) [@kparzysz](https://discuss.tvm.apache.org/u/kparzysz)\
**Post date:** [April 15, 2021, 1:21pm UTC](https://discuss.tvm.apache.org/t/implementing-aot-in-tvm/9206/31 "2021-04-15T13:21:10Z")

</div>

> [@giuseros](#):
>
> From what I understand @kparzysz you are saying that the internal functions don’t matter (they will be static private functions) but that the runner function should have this signature. Can I ask you why?

The reason is that this is the signature that we’re currently using for all TVM-generated functions. To call a function like that all you need to know what parameters the function takes. This is essentially the definition of TVM-specific ABI, but on the level of the C language. This allows compilers to generate the same steps to call any function.

If you want to develop a different ABI, it will need to be used for all external calls to functions generated by TVM, or else we lose that universality.

---

_[View the full topic](https://discuss.tvm.apache.org/t/implementing-aot-in-tvm/9206)._
