Make loop priorities mandatory?
@zweiner2 and I came to the conclusion today that the current advisory role of loop_priorities
is likely a bad idea--why have it if the scheduler is free to ignore it? In addition, this prevents loop_priorities
from being used for semantics. I am now wondering whether that is needed, though.
@zweiner2 mentioned a situation in which incorrect code is generated without proper nesting from add_prefetch
. Upon further thought, I would like to see the example. @zweiner2, could you provide that? I a m wondering whether the required nesting can't/shouldn't be enforced by adding a (so far potenially missing) dependency.