From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Tue Apr  2 02:14:25 2013
Return-Path: <owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id 24D9A3569B3; Tue,  2 Apr 2013 02:14:25 +0200 (CEST)
Delivered-To: sc22wg5@open-std.org
Received: from nag-j.co.jp (nag-j.co.jp [111.68.142.10])
	by www.open-std.org (Postfix) with ESMTP id C9B853569B3
	for <sc22wg5@open-std.org>; Tue,  2 Apr 2013 02:14:18 +0200 (CEST)
Received: from Maru6 (218-42-159-105.cust.bit-drive.ne.jp [218.42.159.105])
	(authenticated bits=0)
	by nag-j.co.jp (8.14.5/8.14.5) with ESMTP id r320EDXB047937
	for <sc22wg5@open-std.org>; Tue, 2 Apr 2013 00:14:16 GMT
	(envelope-from malcolm@nag-j.co.jp)
Message-ID: <500D60A9C87449A195CE618F15982D67@Maru6>
From: "Malcolm Cohen" <malcolm@nag-j.co.jp>
To: "WG5" <sc22wg5@open-std.org>
Subject: Fw: (j3.2006) (SC22WG5.4963) [ukfortran] AW: Thoughts on Reinhold's thoughts
Date: Tue, 2 Apr 2013 09:14:14 +0900
Organization: =?UTF-8?B?5pel5pysTkFH?=
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3555.308
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

This reply forwarded to WG5 since that is where the discussion is taking place.

-----Original Message----- 
From: Van Snyder
Date: 平成 25年4月2日 4:53
To: longb@cray.com ; fortran standards email list for J3
Subject: Re: (j3.2006) (SC22WG5.4963) [ukfortran] AW: Thoughts on Reinhold's 
thoughts

On Mon, 2013-04-01 at 07:46 -0500, Bill Long wrote:
>
> On 3/30/13 8:35 PM, Van Snyder wrote:
> > On Sat, 2013-03-30 at 09:41 +0000, N.M. Maclaren wrote:
> >
> >>>      CHANGE TEAMS would synchronise only the subteam, but would do
> >>> so at beginning and end
> >>
> >
> > If CHANGE TEAMS synchronizes, it ultimately synchronizes all of the
> > images of the current team, but maybe not all of them at the same time.
> > It should be arranged that each subteam has a separate rendezvous, which
> > would be better than requiring all images of the current team to
> > rendezvous before any can proceed.
>
> Separate synchronizations of subteams is what SYNC TEAM does.   If
> that's the model that best fits a particular program, then maybe the
> programmer should consider using SYNC TEAM instead of CHANGE TEAM.

That's only the same if every image does SYNC TEAM.  And then it doesn't
change the team membership.  What is the reason for all images of the
current team to synchronize at CHANGE TEAM?  Does it cause a problem if
each team proceeds as soon as all of its images synchronize, even if
images of other teams haven't yet synchronized?

> Cheers,
> Bill
>
>
>
> >
> >
> > _______________________________________________
> > J3 mailing list
> > J3@mailman.j3-fortran.org
> > http://mailman.j3-fortran.org/mailman/listinfo/j3
> >
>


_______________________________________________
J3 mailing list
J3@mailman.j3-fortran.org
http://mailman.j3-fortran.org/mailman/listinfo/j3

________________________________________________________________________
This e-mail has been scanned for all viruses by Star.
________________________________________________________________________

-- 
................................Malcolm Cohen, Nihon NAG, Tokyo.