search for: 30j

...they follow the linearity. I perform dynamic > instrumentation to compute the coefficients. Mh. I believe we should distinguish the data for Polly and for your calculations. I assumed we would use affine linear relations in the access functions (Actually isl_maps like {[i,j] -> List[10i + 30j + 10]) to define accesses such that Polly can use this access functions to calculate dependences and reschedule 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 &gt...

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){