Hi All.
I just noticed that AutoScheduler lacks support for ExternOp. Currently
AutoScheduler supports ComputeOp only.
I understand that it is non-trial to auto schedule a op with external function
calls, however there are a bunch of topi ops whose algorithm are purely written
with tensor ex
I guess the reason it needs a wrapper is because they are written in TIR
instead of TE? Since AutoScheduler can only tune TE compute, it cannot tune
such ops anyways. On the other hand, the AutoTIR that @junrushao1994 is working
on supports tuning for all levels so you may look forward it.
Me
Currently we don't do any sort of automated testing to make sure our Docker
images are healthy, so it is not uncommon that the images are sometimes broken
and we don't have visibility of the issues. Only when we decide to update the
images, then it causes massive pain (e.g.
https://github.com
Thanks @leandron for the proposal! I agree this will be a great help in
monitoring the container rebuild process for problems and should reduce the
headache typically involved with updating containers.
I think we could prototype this first using
https://discuss.tvm.apache.org/t/ci-how-to-run-
Thank you @comaniac , really appreciate!
The reason "...because they are written in TIR instead of TE" does make sense
to me. And I agree for the case "scatter", the improvement would be small. I
guess Relay's default schedule is probably good enough for my case.
---
[Visit
Topic](https:
