(j3.2006) (SC22WG5.4092) Standard intrinsics and coarrays
Tue Oct 20 06:59:35 EDT 2009
Am I along the right lines here?
We seem to have forgotten to specify how the intrinsic procedures may
be used as far as their use in unordered images is concerned - or, at
least, I can't find anything. However, I don't think that there is much
of a problem. 13.5 paragraph 2 and Table 13.1 is the starting point,
and a lot of my proposal is already implied for those of classes E, ES
and PS by other wording. Those of class A are already covered.
I have drafted the hard line on random numbers; it would be possible to
make the 'shall not' conditional on the processor dependence, but that
In 13.5, Standard generic intrinsic procedures, after Table 13.1, add
the new paragraphs:
EXECUTE_COMMAND_LINE shall not be be called in two unordered images.
RANDOM_SEED shall not be be called in two unordered images, nor
shall RANDOM_NUMBER and RANDOM_SEED be called in two unordered
images. It is processor dependent whether all images use a common
generator or whether each image uses a separate one.
CPU_TIME, DATE_AND_TIME, GET_COMMAND, GET_COMMAND_ARGUMENT,
GET_ENVIRONMENT_VARIABLE and SYSTEM_CLOCK may be called in unordered
images, but it is processor dependent whether the results they return
are dependent on which image calls them.
All other standard intrinsic procedures may be called in unordered
images, subject only to their argument use following the rules in
University of Cambridge Computing Service,
New Museums Site, Pembroke Street, Cambridge CB2 3QH, England.
Email: nmm1 at cam.ac.uk
Tel.: +44 1223 334761 Fax: +44 1223 334679
More information about the J3