From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Mon Apr 6 05:38:03 2015 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 A19DD3585D2; Mon, 6 Apr 2015 05:38:03 +0200 (CEST) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 641 seconds by postgrey-1.34 at www5.open-std.org; Mon, 06 Apr 2015 05:38:02 CEST Received: from esa2.cray.iphmx.com (esa2.cray.iphmx.com [68.232.143.164]) by www.open-std.org (Postfix) with ESMTP id C21EC3568C8 for ; Mon, 6 Apr 2015 05:38:01 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.11,530,1422921600"; d="scan'208";a="1325753" Received: from cray-smtp-2.cray.com (HELO CFWEX01.americas.cray.com) ([136.162.34.11]) by esa2.cray.iphmx.com with ESMTP/TLS/AES128-SHA; 06 Apr 2015 04:27:13 +0100 Received: from CFWEXHYBRID.americas.cray.com (172.30.88.178) by CFWEX01.americas.cray.com (172.30.88.25) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sun, 5 Apr 2015 22:27:12 -0500 Received: from CFWEX01.americas.cray.com ([169.254.1.240]) by cfwexhybrid.americas.cray.com ([::1]) with mapi id 14.03.0224.002; Sun, 5 Apr 2015 22:27:11 -0500 From: Bill Long To: WG5 Subject: Re: (j3.2006) (SC22WG5.5458) New draft TS and straw ballot Thread-Topic: (j3.2006) (SC22WG5.5458) New draft TS and straw ballot Thread-Index: AQHQWyWFWR0J0V/TtkmFXv6hFjUTvp0/0KgA Date: Mon, 6 Apr 2015 03:27:10 +0000 Message-ID: References: <20150310112934.28EC1357206@www.open-std.org> In-Reply-To: <20150310112934.28EC1357206@www.open-std.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.233.197] Content-Type: text/plain; charset="Windows-1252" Content-ID: <833780F7F045C14D8BBBAAE52967CACC@cray.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: owner-sc22wg5@open-std.org Precedence: bulk On Mar 10, 2015, at 6:29 AM, John Reid wrote: Please answer the following question "Is N2048 ready for forwarding to=20 SC22 as the PDTS?" in one of these ways.=20 1) Yes. 2) Yes, but I recommend the following changes.=20 3) No, for the following reasons. 4) Abstain. This is an individual vote. Please send your vote to sc22wg5@open-std.org=20 to arrive by 9 a.m. (UK time) on 7 April 2015.=20 Answer: 2) Yes, but I recommend the following changes. As noted by Van, the description of the CRITICAL statement is incomplete. Van's suggested rewording didn't distinguish between executing a CRITICAL statement (several images could have started doing that) and completing execution of the CRITICAL statement (which happens on the image we really care about, the one that starts executing the block). Also, I think it would be better to edit the base standard to put the STAT=3D and ERRMSG=3D description in 8.5.7 and have a reference to 8.5.7 in 8.1.5. Other image control statements use that convention. The following alternate wording was proposed by John, and I agree it addresses the issues. Edits to N2048: [16:5-7] Replace the sentence "In the CRITICAL ... execute the=20 construct." by a new paragraph: "If the processor has the ability to detect that an image has failed,=20 when an image completes execution of a CRITICAL statement that has a=20 STAT=3D specifier and the previous image to have entered the construct failed while executing it, the specified variable becomes defined=20 with the value STAT_FAILED_IMAGE from the intrinsic module=20 ISO_FORTRAN_ENV. Otherwise, when an image completes execution of a=20 CRITICAL statement that has a STAT=3Dspecifier, the specified variable=20 becomes defined with the value zero. When an image completes execution=20 of a CRITICAL statement that has an ERRMSG=3D specifier and assigns a=20 nonzero value to the status variable of a STAT=3D specifier or would=20 have done so if a STAT=3D specifier had appeared, the processor shall=20 assign an explanatory message to the specified variable as if by=20 intrinsic assignment." [37:4] Before "}" add 'After para 3, add a new para: "The effect of a STAT=3D or an ERRMSG=3D=20 specifier in a CRITICAL statement is explained in 8.5.7."' [38:40] Before "}" add=20 "the following paragraphs, then add the final paragraph of 6.3=20 CRITICAL construct of this Technical Specification.=94 Bill Long = longb@cray.com Fortran Technical Suport & voice: 651-60= 5-9024 Bioinformatics Software Development fax: 651-605-9142 Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101