Would it make sense to use natural_vector_size() instead of a hardcoded number in the generated code?
It would serve two purposes:
Convey a tangible reason for a schedule to a new user (rather than a magic number)
Make it slightly easier to compare schedules when tweaking it for multiple targets. i.e say I was tuning for AVX and another for AVX2, using natural_vector_size() will potentially reduce the difference between the two and in some cases eliminate the need to have two different schedules in the generator.
Would it make sense to use natural_vector_size() instead of a hardcoded number in the generated code? It would serve two purposes: