I agree that having a common prefix is helpful in the dso landscape to clearly
identify function generated by tvm. To faciliate discussion, consider the
following code
```python
m = tvm.runtime.load_module("x.so")
# Option P0: require explicit query using tvm_run
run = m["tvm_run"]
# Option P1: the underlying symbol is "tvm_run"
run = m["run"]
```
I believe we are still talking about P0 atm for simplicity(direct
correspondence of symbol and packed func name), but allow the AOT generator to
append a prefix(like @areusch 's comment of prefix starting from char 0). My
main comment of backward compact is when we start to choose P1. If we go with
P1, then we will need to put more thoughts into it.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/mini-rfc-name-mangling-in-aot/9907/9)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.apache.org/email/unsubscribe/95eda1633dc5d95326e90f215a951163bc873289b75a83e7d172f8041985a94b).
