# \[pre-RFC\] Compilation Configuration Representation

**URL:** <https://discuss.tvm.apache.org/t/pre-rfc-compilation-configuration-representation/11372>\
**Category:** RFC\
**Created:** [November 1, 2021, 2:17pm UTC](https://discuss.tvm.apache.org/t/pre-rfc-compilation-configuration-representation/11372 "2021-11-01T14:17:27Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**Author:** ![Mousius](https://discuss.tvm.apache.org/user_avatar/discuss.tvm.apache.org/mousius/32/2607_2.png) [@Mousius](https://discuss.tvm.apache.org/u/Mousius)\
**Post date:** [November 11, 2021, 7:22pm UTC](https://discuss.tvm.apache.org/t/pre-rfc-compilation-configuration-representation/11372/33 "2021-11-11T19:22:37Z")

</div>

> [@junrushao](#):
>
> On the other hand, my concern is the fragmentation of APIs. It has been a huge problem in the recent 1-2 years, and we do have alternatives not to do so.

Could you elaborate on this? I believe this isn’t solely a UX issue but also a hygiene factor within the compiler and how we represent the data structures internally so would rather not overload `Target` with `Executor` and `Runtime`. This RFC is proposing a suitable home for information that’s relevant across the compilation given we now have at least `Executor` and `Runtime` to include, but a side effect is bringing the `tvmc` view back into alignment with the internals of the compiler.

It’s also worth noting, that with the current RFC for [Migrating Target Attributes to IRModule](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0029-migrating-to-irmodule-attributes.md) `tvmc` can glue this together with the relevant pieces, so from a user point of view they wouldn’t know how disparate the internals are but it would be a headache to maintain.

---

_[View the full topic](https://discuss.tvm.apache.org/t/pre-rfc-compilation-configuration-representation/11372)._
