(j3.2006) DEALLOCATE and image control

[Van Snyder]

On Fri, 2014-04-04 at 15:25 +0900, Malcolm Cohen wrote:
> >While thinking about this, and having found 6.7.3.2p8, I started 
> >wondering the order in which allocatable components of allocatable 
> >objects are deallocated.  It should be specified,
> 
> It is specified.  It is processor dependent.  6.7.3.1p4.
> 
> > perhaps "in component order."
> 
> No.
> 
> >  If there are, say, two allocatable coarray components, and one 
> >image deallocates them in one order, while another one deallocates in 
> >another order, deadlock results.
> 
> Well the processor had better not do that then.  For that matter
>   DEALLOCATE(coarray1,coarray2)
> had better not deadlock (no allocatable components in sight here).

Perhaps it ought to be stated that all images shall deallocate
<allocate-object>s in the same order, and all allocatable components in
the same order.