As more a policy kind of comment, for a fix release and the potential for more,
as a community, "we" might want to set some expectations for how long something
might be maintained / update frequency etc kind of akin to the linux kernel
community. (ex: https://www.kernel.org/category/releases.h
Yap, or choose TIR lowering for some sub-functions :)
---
[Visit
Topic](https://discuss.tvm.ai/t/rfc-ethosn-arm-ethos-n-integration/6680/19) to
respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.ai/em
By this do you mean, for instance, paritioning a graph for GPU/CPU with both
going via TIR lowering?
---
[Visit
Topic](https://discuss.tvm.ai/t/rfc-ethosn-arm-ethos-n-integration/6680/18) to
respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these
We could, but given that it is not strictly a bug, we can also choose not to
---
[Visit
Topic](https://discuss.tvm.ai/t/rfc-minor-bugfix-release-for-v0-6/6716/4) to
respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](http
I want to followup that the general infrastructure of pattern matching and
rewriting does not conflict with AutoTVM.
It is important to follow a composite view to the infrastructure, and view BYOC
as natural feature by combining parts of the infrastructure together, rather
than a monotholic
You covered the main advantages. You could add a thriving OSS community.
With BYOC it is fairly easy to add a new backend, depending on exactly what you
want to do. If one of the TVM runtimes matches your use-case then it is worth
considering. It also depends of course on what alternatives you
When try to apply a pattern on a control flow IR, it crashes
Is it expected? Should I get data flow block before using rewrite or partition
or is pattern language supposed to work in each data flow block?
This is the patch to reproduce
```
diff --git a/tests/python/frontend/tensorflow/test_co
So I want to konw what's the benefit about BYOC. I list some advantanges:
1: if the new backend doesn't support all ops, we can back to cpu
2: use rely to support different frameworks
3: some graph level optimizes(can we use all graph level optimizes?)
But tvm maybe too heavy for newbackend.
You are right; we leverage the existing compiler/optimiser (the support
library) for Ethos-N, see https://github.com/ARM-software/ethos-n-driver-stack.
Integration at the relay level makes sense for the type of operations that are
implemented in Ethos-N.
The accelerator is always faster than a
I have a question why you choose BYOC. We can't use AutoTVM in BYOC and I think
AutoTVM is the very import feature of TVM.
---
[Visit
Topic](https://discuss.tvm.ai/t/rfc-ethosn-arm-ethos-n-integration/6680/13) to
respond.
You are receiving this because you enabled mailing list mode.
To
10 matches
Mail list logo
