[OpenCoarrays] Re: Block construct and sync all behavior

Damian Rouson damian@sourceryinstitute.org
Tue Oct 21 15:54:00 GMT 2014




On Oct 21, 2014, at 8:46 AM, N.M. Maclaren <nmm1@cam.ac.uk> wrote:

> On Oct 21 2014, Damian Rouson wrote:
>> 
>> But, as you say, I/O synchronisation is
>>> not part of the coarray design or gfortran run-time system.  
>> 
>> That's fine as a design decision, but what in the standard communicates this design decision? When I read "8.5.3 SYNC ALL statement" in a draft of the Fortran 2008 standard, I see nothing that would make it clear to a novice that segment ordering does not imply ordering of I/O. It would be nice to see a note of warning.
> 
> Grrk.  You have a point.  That is implied (vaguely) by Note 9.15, but
> doesn't seem to be stated anywhere.  Nor whether the merging preserves
> record boundaries which, in practice, it won’t.

Yes, that was exactly my thought when 9.15 was mentioned.  It’s not clear that a merge implies the possibility of record boundaries being reordered. 

Damian


More information about the Fortran mailing list