It uses the target specified in MeasureInput. See L428 in
https://github.com/apache/incubator-tvm/blob/master/python/tvm/autotvm/measure/measure_methods.py
---
[Visit
Topic](https://discuss.tvm.apache.org/t/localrunner-and-rpcrunner/7959/4) to
respond.
You are receiving this because you
Thanks for the explanation! I'm looking at the LocalBuilder function in both
the CPU and GPU tutorials, but neither of them takes any arguments related to
the target. How does the builder know about the target?
> tuning_option = {
> "log_filename": log_file,
> "tuner": "xgb",
> "n_
The hardware related information is specified in "target". In your case, the
target should be `cuda -model=1080ti`. The builder will build the model based
on the target, and runner is only in charge of running the built model, so it
doesn't have to take the hardware information. Accordingly, t
@haichen, I'm trying this, but the alter_op_layout is never called because the
layouts appear to be invalid. Specifically, this line
https://github.com/apache/incubator-tvm/blob/master/src/relay/transforms/transform_layout.h#L285-L286
always returns `success=false`. I tried adding the `Elemwis
Hi there,
I'm a newbie to TVM and I'm trying to get started with the tuning tutorial for
x86 and NVIDIA GPU. My question is about the Runners. It seems like the
LocalRunner itself does not distinguish the backend that the tuning is done
for, but the tuning by itself should be specific to hard
