@anwang Ansor also has a "task" concept. A task is not necessary to be just for one operator. It just means a "tuning" task. As a result, I still vote for task.
In addition, I don't think full enumeration is proper for several reasons. 1. Full enumeration will lose the flexibility when adding new tasks. 2. It would make the log too long and tedious, because the task arguments (attributes) are very different. For example, this is the task arguments for `conv2d_NCHWc.x86`: https://github.com/apache/incubator-tvm/blob/master/topi/python/topi/x86/conv2d.py#L149 And this is `dense.nopack.x86`: https://github.com/apache/incubator-tvm/blob/master/topi/python/topi/x86/dense.py#L138 You can basically search for `autotvm.register_topi_compute` in TOPI to see all task function arguments. Unless we can also canonicalize the task arguments, it seems impractical have a full enumeration argument list. Consequently, IMHO, supporting arbitrary kwargs arguments would be more practical. --- [Visit Topic](https://discuss.tvm.ai/t/rfc-canonicalizing-autotvm-log-format/7038/23) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/aab74f165fa33fdbbd90ee6e519c21457cbb90c0acd92c78b7bfe01d21c3d33a).
