http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53526
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-06-01 17:54:42 UTC --- MOVE_ALLOC - following the current interpretation request - seems to be more complicated that I had imagined: It's unclear to me whether the users have to invoke it on all images (like allocate/deallocate) or not. If not, one gets into all kind of issues. See: http://j3-fortran.org/pipermail/j3/2012-June/005312.html Assuming that the user has to call it on all images, the current patches are: - check.c: http://gcc.gnu.org/ml/fortran/2012-05/msg00171.html - trans-intrinsic.c: http://gcc.gnu.org/ml/fortran/2012-05/msg00173.html In the latter, the SYNC ALL should be replaced by SYNC MEMORY, which is all what is implied by an image control statement. (It cannot be nothing as some changes before MOVE_ALLOC might have to be flushed.) Or might might remain SYNC ALL - which is required to avoid inconsistency issues [assuming that it has to be called on all images].
