(j3.2006) (SC22WG5.5484) New draft TS and straw ballot

[Bill Long]

On Mar 10, 2015, at 6:29 AM, John Reid <John.Reid at stfc.ac.uk> wrote:


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

1) Yes.
2) Yes, but I recommend the following changes. 
3) No, for the following reasons.
4) Abstain.

This is an individual vote. Please send your vote to sc22wg5 at open-std.org 
to arrive by 9 a.m. (UK time) on 7 April 2015. 

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= and ERRMSG= 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 
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.?




Bill Long                                                                       longb at cray.com
Fortran Technical Suport  &                                  voice:  651-605-9024
Bioinformatics Software Development                     fax:  651-605-9142
Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101