TVM code generation has redundant border?

Hey, I am not 100% sure but maybe if you look in this post you will see what might be the cause.

Even though the linked post is old and I think there wasn’t a definite answer, the schedule.normalize() will bring all the loops to a common representation (in this case since C can be embedded in the iteration space of F, the boundaries are those of F)