From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Fri Apr 1 19:44:57 2016 Return-Path: X-Original-To: sc22wg5-dom8 Delivered-To: sc22wg5-dom8@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 282173587C0; Fri, 1 Apr 2016 19:44:57 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from postout1.mail.lrz.de (postout1.mail.lrz.de [129.187.255.137]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id F13BA3582C8 for ; Fri, 1 Apr 2016 19:44:55 +0200 (CEST) Received: from lxmhs51.srv.lrz.de (localhost [127.0.0.1]) by postout1.mail.lrz.de (Postfix) with ESMTP id 3qc80R0GLfzyT5; Fri, 1 Apr 2016 19:44:55 +0200 (CEST) Authentication-Results: postout.lrz.de (amavisd-new); dkim=pass (2048-bit key) reason="pass (just generated, assumed good)" header.d=lrz.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lrz.de; h= mime-version:content-transfer-encoding:content-type:content-type :content-language:accept-language:in-reply-to:references :message-id:date:date:subject:subject:from:from:received :received:received:received; s=postout; t=1459532694; bh=1mrJyaB ffdhOkFGMF0sy4lpo+1nkEonNOH9rPBbIkM8=; b=pXkyv6v6nhv8LWCjMOccCYN BsZi/JA4rgLnUjq65B5jCdrHgSqh7X95wo62up5iCXtQy0yVnQHuGt8nrTyDA3hD HXq2aiv81aooqHefFlU2Rc2ZiO1WS3fxNBknOoBaoXOFjJfCxusa+sxPGlM9kA0N CKIm3TwTlyffC/OvSqz5Z7jflhvNmXGjs68eOOUod/C/E0NSVMFnARalutHAEaH8 BhGGVF/nYpO5POMVyCHeBxjPXds4ht98ysX35eJhV72CoCqBSLkNkj3xRaUiGJEa jOnj4Y/2lG8VtPC0Vbw8APuFepmpMfTRveLK+sQZGLoKsmDi6JHnGc6ktbNrp7Q= = X-Virus-Scanned: by amavisd-new at lrz.de in lxmhs51.srv.lrz.de X-Spam-Flag: NO X-Spam-Score: -2.885 X-Spam-Level: X-Spam-Status: No, score=-2.885 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, LRZ_DATE_TZ_0000=0.001, LRZ_DKIM_DESTROY_MTA=0.001, LRZ_DMARC_LRZ_FAIL=0.001, LRZ_DMARC_OVERWRITE=0.001, LRZ_ENVFROM_LRZ_S=0.001, LRZ_FROM_AP_PHRASE=0.001, LRZ_FROM_LRZ_S=0.001, LRZ_FROM_PHRASE=0.001, LRZ_FROM_PRE_SUR_ADDR=0.001, LRZ_FWD_MS_EX=0.001, LRZ_HAS_X_ORIG_IP=0.001, LRZ_MSGID_HL32=0.001, LRZ_MSGID_SPAM_68=0.001, LRZ_RCVD_MS_EX=0.001, SPF_HELO_NONE=0.001] autolearn=no autolearn_force=no Received: from postout1.mail.lrz.de ([127.0.0.1]) by lxmhs51.srv.lrz.de (lxmhs51.srv.lrz.de [127.0.0.1]) (amavisd-new, port 20024) with LMTP id kK705P4RAbQv; Fri, 1 Apr 2016 19:44:54 +0200 (CEST) Received: from BADWLRZ-SW13MB6.ads.mwn.de (BADWLRZ-SW13MB6.ads.mwn.de [IPv6:2001:4ca0:0:108::154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "BADWLRZ-SW13MB6", Issuer "BADWLRZ-SW13MB6" (not verified)) by postout1.mail.lrz.de (Postfix) with ESMTPS id 3qc80Q2dLVzySb; Fri, 1 Apr 2016 19:44:54 +0200 (CEST) Received: from BADWLRZ-SWMBX03.ads.mwn.de (2001:4ca0:0:108::159) by BADWLRZ-SW13MB6.ads.mwn.de (2001:4ca0:0:108::154) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Fri, 1 Apr 2016 19:44:53 +0200 Received: from BADWLRZ-SWMBX03.ads.mwn.de ([fe80::7c52:cc37:21a8:1966]) by BADWLRZ-SWMBX03.ads.mwn.de ([fe80::7c52:cc37:21a8:1966%12]) with mapi id 15.00.1156.000; Fri, 1 Apr 2016 19:44:53 +0200 From: "Bader, Reinhold" To: fortran standards email list for J3 CC: WG5 Subject: AW: (j3.2006) (SC22WG5.5694) coarray dummy arguments Thread-Topic: (j3.2006) (SC22WG5.5694) coarray dummy arguments Thread-Index: AdGLIjqiwNtJ9t9cQqCzYaSC3aToTwAUp2OAADEPAkA= Date: Fri, 1 Apr 2016 17:44:53 +0000 Message-ID: <0cf14105fae4499aa3479b65f4e6d150@BADWLRZ-SWMBX03.ads.mwn.de> References: <20160331075716.B092135872B@www.open-std.org> <20160331124346.5599A3587B1@www.open-std.org> In-Reply-To: <20160331124346.5599A3587B1@www.open-std.org> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [2001:4ca0:0:f034::1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: owner-sc22wg5@open-std.org Precedence: bulk Hi Bill,=20 > -----Urspr=FCngliche Nachricht----- > Von: j3-bounces@mailman.j3-fortran.org [mailto:j3-bounces@mailman.j3- > fortran.org] Im Auftrag von Bill Long > Gesendet: Donnerstag, 31. M=E4rz 2016 14:44 > An: fortran standards email list for J3 > Cc: WG5 > Betreff: (j3.2006) (SC22WG5.5694) coarray dummy arguments >=20 > Hi Reinhold, >=20 > In your second edit, "after Note 2.34.", change "after" to "before", or m= ade > the citation [307:5+] and start the edit "after 12.5.2.8p2.". The Notes= should > all be together at the end of the subclause. OK.=20 >=20 > In the same edit as above, at the end of the new text, delete "on the cur= rent > team", since it is possible to access objects on images that are part of = a > different team. This does not apply for coarray dummy arguments. See TS 18508 [9:23+],=20 at least not at the time the procedure starts execution. >=20 > The wording that prohibits the copy-in/copy-out problem is 12.5.2.8p2. My understanding was that that paragraph is a requirement on the user progr= am that avoids a situation where the processor would be *obliged* to do copy-in / o= ut.=20 It therefore doesn't go far enough. >=20 > For the [312] Note 12.39+, an example of a case that is not already cover= ed by > existing rules would be helpful. I found the note confusing. I'm not su= re how > image control statements would avoid argument aliasing problems. Consider the following procedure SUBROUTINE S1(A, IL) INTEGER :: A INTEGER :: IL IL =3D A END SUBROUTINE and the following execution flow on 2 images: Image 1:=20 INTEGER :: I[*] =3D 0 I[2] =3D I[2] + 1 SYNC IMAGES( [1,2] ) Image 2: INTEGER :: IL SYNC IMAGES( [1,2] ) CALL S1(I, IL) For this case, the image control statements must be outside the subroutine.= If A were declared as a coarray dummy in S1, one could move the SYNC IMAGES on image 2 inside the procedure= .=20 However I agree that the wording of the note is confusing. I'll either remo= ve the last part of it or change it to be clearer. Cheers Reinhold >=20 > Cheers, > Bill >=20 >=20 >=20 > On Mar 31, 2016, at 2:56 AM, Bader, Reinhold wrot= e: >=20 > > Dear all, > > > > attached please find the draft for an attempt to fix issues with coarra= y dummy > arguments that were identified > > in a coarray-ts discussion quite some time ago. I intend to upload it t= o the J3 > server unless serious objections arise. > > > > Cheers > > Reinhold > > > > > > > _______________________________________________ > > J3 mailing list > > J3@mailman.j3-fortran.org > > http://mailman.j3-fortran.org/mailman/listinfo/j3 >=20 > Bill Long = longb@cray.com > Fortran Technical Support & voice: 651= -605-9024 > Bioinformatics Software Development fax: 651-605-914= 2 > Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101 >=20 >=20 > _______________________________________________ > J3 mailing list > J3@mailman.j3-fortran.org > http://mailman.j3-fortran.org/mailman/listinfo/j3