(j3.2006) (SC22WG5.5137) image selectors

Bill Long longb
Mon Dec 9 18:18:35 EST 2013



On 12/9/13 5:05 PM, Van Snyder wrote:
>> OK.  Reinhold's revised ballot reworded this idea in terms of the image
>> >index in the initial team rather than physical processors.  That is
>> >arguably better terminology to use.  The image's image index in the
>> >initial team never changes throughout the program execution.

> I assume this refers to Reinhold's message of 2 December.  That
> message's attachment did not include any comments concerning 5.1.  The
> problem is that "image indices are relative to a specified team" at
> [9:5-6] does not give any information concerning the correspondence
> between coindices in parent teams and subteams, nor does "cosubscripts

See [11:21-22].  The program can explicitly specify the new image index. 
Otherwise it is processor dependent.

> are interpreted as if the current team were the team specified by
> <team-variable>" at [11:4].  Without standardizing this, indexing with
> respect to ancestor teams is not useful.  I tried in vain to find this
> mapping in 5.3 -- 5.5.  The addition of DISTANCE to THIS_IMAGE doesn't
> seem to do the job.
>
> By the way, the edit for 13.7.165 at [33:7] needs "a" before "member".

Right, thanks.  Added to my mark-up copy.

Cheers,
Bill

>

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





More information about the J3 mailing list