Explicit control over loop partitioning #5204
Description
Loop partitioning should be controllable with a scheduling directive. It sucks when I want to partition an outer loop over y and have tiles near the edge computed using separate code from tiles near the middle, and instead some inner loop over a convolution kernel gets split. The reverse is annoying too. I should be able to say which loop is going to be partitioned if any.