Ah you're right. In this case auto-scheduler doesn't differentiate reshape ops, because their names are defined in the TOPI compute (and are the same...). I had this issue before but it was for `cache_read`, which was added by the auto-scheduler so I could let auto-scheduler control its name.
We may need to improve the printer here (https://github.com/apache/tvm/blob/main/src/auto_scheduler/compute_dag.cc#L1206) by adding a renaming logic. I'll try to take a look if I got time in this week. --- [Visit Topic](https://discuss.tvm.apache.org/t/print-auto-schedule-python-schedule-with-topi-op/11363/4) 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/6b2445d8a02c150a68e30185dc33bf9e4d26c5c37bb3a98e80e8b89643394b43).
