search for: conosideration

...eschedule the code accordingly. The possibly non-affine accesses would then be hidden behind the virtual access. > However, for applying the transformations, Polly should either totally > ignore the virtual accesses, or assign some default values to the > coefficients and take them into conosideration. Our plan is to create > several versions, some with different values, lets say a = 1, b= 1, c = > 0, and one version where all the virtual accesses are ignored. What do you mean by totally ignoring the virtual accesses? This would mean Polly would not detect any dependences at all and we w...

This is exactly want I need to achieve with Polly actually. I think a good idea would be to define intrinsics / metadata, as you mentioned, to notify Polly that even though it cannot analyse these accesses, to ignore them and perform the code transformations. We can go even further and maybe describe these accesses with some parametric linear functions. For instance: while (cond1){