hi @manupa-arm,
seems like we have two options:
O1. build a library version of this [StaticRuntime fcompile
function](https://github.com/areusch/incubator-tvm/blob/utvm-runtime/python/tvm/micro/build.py#L217)
and make `export_library` call this function to create something like a DSO
(instea
- For auto-schedule details, you can refer to the paper:
https://arxiv.org/abs/2006.06762
- XGBoost model also takes some features extracted from the TIR.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/autotvm-how-is-the-search-space-being-generated/7982/4)
to respond.
You are receiv
I've seen that current uTVM flow uses module.save(..) interface to save the "c"
module prior to compiling it to the micro binary that is fed to the runtime. I
was wondering if we use the BYOC on the flow and create our own external
c-source module/function additionally to the single dso_module
I don't know why relay drop it, but i think @tqchen @jroesch maybe know more
information and background.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/do-layer-names-get-imported-into-relay/7986/4)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubsc
Thanks for the reply.
I noticed that at least the inputs, weights and biases get the name
/ (so for example 'conv2d_1/input'
would be the IFM of the 'conv2d_1' layer from the model). So I guess over the
naming of the arguments its possible to determine some relationships between
relay operat
Previous IR (NNVM) has one name attribute but relay miss it.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/do-layer-names-get-imported-into-relay/7986/2)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https:/
