This is a good question. This is possible for the current implementation, because we use Relay op strategy to define auto_scheduler tasks as well. In other words, we use Relay FuseOps to define the task scope, and should be able to choose to use TOPI (AutoTVM) or auto_scheduler schedule for each task. However, as you pointed out, this option becomes unavailable after this RFC as we separate their task extraction and compilation paths.
An alternative solution might be keeping all approaches in the same place. Specifically, we still keep the current task extraction (i.e., having `strategy.add_auto_scheduler` in Relay op strategy). When `use_topi_schedule=True`, we can still extract auto_scheduler tasks as for now. The case of `use_topi_schedule=False` would become totally optional. What do you think about this proposal, or do you have any suggestion on this? Also cc @merrymercy. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-a-general-task-extraction-mechanism-for-auto-scheduler/8444/12) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/a2806691c9a958baeb4fc45c0b6770e2c688d1c2c9916b21ddcbd8da83a4e7a3).
