# \[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:** 12

<div class="post-metadata">

**Author:** ![tqchen](https://discuss.tvm.apache.org/user_avatar/discuss.tvm.apache.org/tqchen/32/5_2.png) [@tqchen](https://discuss.tvm.apache.org/u/tqchen)\
**Post date:** [November 4, 2021, 1:19pm UTC](https://discuss.tvm.apache.org/t/pre-rfc-compilation-configuration-representation/11372/12 "2021-11-04T13:19:07Z")

</div>

Thanks @manupa-arm , building on what you said.

- I do not think there is a strong contention on C1, the main point is that the target can be recursive. So a target like the follows is totally OK.

```bash
- kind: hetro-exec
- runtime : crt
- executor: vm
- devices: [se_scope0, se_scope1]

```

So the argument is not about where/or how these field should be structured in a recursive data structure. Something that looks like a CompilationOption is OK from my pov. But the suggestion is that we make that one kind of (recursive) target, as from UX’s pov it can be seen that way.

- I want to add C3: The ability to leverage tagging in target and improve the overall user experience is a very important factor.

I am going to discuss C2 on a separate post since that worths more examples.

---

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