[OpenCoarrays] RFC patch: Dependency/alias analysis wir same-image coarray access

[Alessandro Fanfarillo]

On Wed, Aug 27, 2014 at 2:45 PM, Tobias Burnus <burnus@net-b.de> wrote:
> However, crucially is really the case (3), where the library has to generate
> a temporary array – independent whether the library handles overlapping
> memory access or not - and independently whether memmove is used or not.
> Prime example is - as I showed before - the case "a(10:2:-1)[1] = a(:)"
> where in a forward access to the memory, you have already overridden the
> memory location with a value before you read from it. (In that case, it
> helps what memmove does in that case: If you cannot walk forward, then walk
> backwards. But with multiple dimensions, one can create more complicated
> pattern.)
>
> Tobias

I see the problem here. Good point.

-- 

Alessandro Fanfarillo