Open nmnobre opened 1 year ago
I can have a look, but I am rather busy, will be a week or two probably before I can get to that. I also haven't touch the dependency handling code for a few months, so it will take me some time to get back into it.
This pattern is found in several more places in NEMO like zdfsh2.f90
and dynvor.f90::vor_een
.
It needs:
I realise this might be hard to solve, but in cases such as:
ztmp
prevents parallelisation of the outer loop via a WaW dependence.However, we can see that
ztmp
is overwritten exactly over the same range in each iteration of the outer loop and that the only use is after the write in the program's text. So, at most, only the last iteration's writes might matter outside the loop. Furthermore, if I force parallelisation by ignoring the dependence analysis results,ztmp
isn't marked private and remains shared. I know I'm asking for trouble here, but do we think this might be supported one day?