for A2, we should consider the type of options present:
- options that serve to specify how a pass runs should eventually find their
way into the active `PassContext`
- options which are constraints can be attached to `Target` or similar.
I think we could use [Target-registered compilation flow
@areusch it is ready for another look
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/63#issuecomment-1104314240
You are receiving this because you are subscribed to this thread.
Message ID:
> @leandron, looking at Docker Hub (https://hub.docker.com/_/hello-world) it
> would appear the convention for image names is to use `-` there as well (i.e.
> `tlcpack/ci-cpu` rather than `tlcpack/ci_cpu`) can we go for that one?
Sure. I’ll push an updated version with this and @gromero’s sugges
@leandron, looking at Docker Hub (https://hub.docker.com/_/hello-world) it
would appear the convention for image names is to use `-` there as well (i.e.
`tlcpack/ci-cpu` rather than `tlcpack/ci_cpu`) can we go for that one?
--
Reply to this email directly or view it on GitHub:
https://github.c
Just friendly note here, that as I'm not hearing opposition, I'll move into
creating a a PR to update the documentation and reflect the changes proposed
here where appropriate.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/66#issuecomment-11041171
