What about we define a new target kind:
```
{
"kind": "packaged", # probably need a better name, please propose new ones
"runtime": "crt", # the "runtime" in the proposal
"executor": { # the codegen target for relay function
# i.e. the "executor" in the proposal
"kind": "vm/aot",
...
},
"target": {
"kind": "cuda", # the target that TIR generates to
"host": {
"kind": "llvm", # the codegen target for the host-side driver code
...
}
},
}
```
We can provide helpers to sugar the construction of this recursive target:
```python
def tvm.target.packaged(
target="cuda",
executor="aot",
runtime="crt",
): ...
```
In the common case, user only need to feed with "cuda", because we could
provide a good default. For advanced use cases, users could use the packaged
API to specify their own specification for the package
---
[Visit
Topic](https://discuss.tvm.apache.org/t/pre-rfc-compilation-configuration-representation/11372/36)
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/b6de79fb08c829db7416cce66b8d996188ea6438d7307de95750016025848fa8).
