From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Mon Apr  6 13:50:29 2015
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 909DF9DB142; Mon,  6 Apr 2015 13:50:29 +0200 (CEST)
Delivered-To: sc22wg5@open-std.org
Received: from out.ipsmtp3nec.opaltelecom.net (out.ipsmtp3nec.opaltelecom.net [62.24.202.75])
	by www.open-std.org (Postfix) with ESMTP id E6FD33568FD
	for <sc22wg5@open-std.org>; Mon,  6 Apr 2015 13:50:24 +0200 (CEST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2CVAQCHciJV/8p3L1ANT4dLyggBAQEBAQGFRhUbWwIFIQIRAkwNCAK7KHCSPIUHDAEfgSGRcIFFBZptgR2DNZACgiUcgVGDMQEBAQ
X-IPAS-Result: A2CVAQCHciJV/8p3L1ANT4dLyggBAQEBAQGFRhUbWwIFIQIRAkwNCAK7KHCSPIUHDAEfgSGRcIFFBZptgR2DNZACgiUcgVGDMQEBAQ
X-IronPort-AV: E=Sophos;i="5.11,531,1422921600"; 
   d="scan'208";a="531008888"
Received: from host-80-47-119-202.as13285.net (HELO [192.168.1.4]) ([80.47.119.202])
  by out.ipsmtp3nec.opaltelecom.net with ESMTP; 06 Apr 2015 12:50:23 +0100
Message-ID: <552272FD.30608@stfc.ac.uk>
Date: Mon, 06 Apr 2015 12:50:21 +0100
From: John Reid <John.Reid@stfc.ac.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1
MIME-Version: 1.0
To: WG5 <sc22wg5@open-std.org>
Subject: WG5 straw ballot on N2048
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

Please answer the following question "Is N2048 ready for forwarding to
SC22 as the PDTS?" in one of these ways.

2) Yes, but I recommend the following changes.

At the Feb. meeting of J3, we did not complete the changes needed for 
when an image fails while executing a CRITICAL construct. I suggest 
these edits to N2048.


[16:5-7] Replace the sentence "In the CRITICAL ... execute the
construct." by a new paragraph:
"If the processor has the ability to detect that an image has failed,
when an image completes execution of a CRITICAL statement that has a
STAT= specifier and the previous image to have entered the construct
failed while executing it, the specified variable becomes defined
with the value STAT_FAILED_IMAGE from the intrinsic module
ISO_FORTRAN_ENV. Otherwise, when an image completes execution of a
CRITICAL statement that has a STAT=specifier, the specified variable
becomes defined with the value zero. When an image completes execution
of a CRITICAL statement that has an ERRMSG= specifier and assigns a
nonzero value to the status variable of a STAT= specifier or would
have done so if a STAT= specifier had appeared, the processor shall
assign an explanatory message to the specified variable as if by
intrinsic assignment."

[37:4] Before "}" add
'After para 3, add a new para: "The effect of a STAT= or an ERRMSG=
specifier in a CRITICAL statement is explained in 8.5.7."'

[38:40] Before "}" add
"the following paragraphs, then add the final paragraph of 6.3
CRITICAL construct of this Technical Specification."