(j3.2006) MOVE_ALLOC with coarrays: Add STAT= for STAT_STOPPED_IMAGE?

[Bader, Reinhold]

I agree. 

Also, even if the DEALLOCATE in itself does not fail, adding the STAT is necessary to enable continuing execution with failed images in the current team (as far as the TS is concerned).

Regards
Reinhold



> -----Urspr?ngliche Nachricht-----
> Von: j3-bounces at mailman.j3-fortran.org [mailto:j3-bounces at mailman.j3-
> fortran.org] Im Auftrag von Tobias Burnus
> Gesendet: Mittwoch, 23. Oktober 2013 20:11
> An: fortran standards email list for J3
> Betreff: (j3.2006) MOVE_ALLOC with coarrays: Add STAT= for
> STAT_STOPPED_IMAGE?
> 
> Hi all,
> 
> this email is motivated by a question in comp.lang.fortran by someone
> who observed that ALLOCATE/DEALLOCATE statements have a STAT=/ERRMSG=
> while MOVE_ALLOC doesn't.
> 
> For noncoarrays, I think MOVE_ALLOC can be treated as any user procedure
> with intent(out) allocatable arguments, for which also no error
> diagnostic exists and where deallocation is unlikely to fail.
> 
> However, for coarrays MOVE_ALLOC is also an image control statement ?
> and collective deallocation is much more likely to fail (e.g. with
> STAT_STOPPED_IMAGE). Thus, one might consider adding "dealloc-opt"-like
> optional dummy arguments for error recovery.
> 
> Tobias
> _______________________________________________
> J3 mailing list
> J3 at mailman.j3-fortran.org
> http://mailman.j3-fortran.org/mailman/listinfo/j3