tvm-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lianmin Zheng <>
Subject Re: [dmlc/tvm] [RFC][AUTOTVM] Auto-Schedule from Compute Declaration (#2954)
Date Thu, 04 Apr 2019 10:30:19 GMT
@jroesch There is no easy description for a backend. Currently these meta-templates are mainly
based on the summary of existing human schedule code in TOPI. So adding a new backend is still
hard. What can be reused is the classification of compute type.

@kevinthesun There is only one template for one specific op. The auto-scheduler first creates
this template. Then, for static usage, it will fill the knobs in the template according to
hardware paremeters. The example shown above falls in this category. For tuning usage, the
auto-scheduler won't use hardware parameters. Instead, it relies real tuning. In this case,
you need to explicitly create `autotvm.Task`, `autotvm.Tuner`. An example is shown in the

@yzhliu The `tvm.compute` dsl is much easier to analyze than general Halide IR, because of
its clean dependency relations and well-defined loop structure.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message