Clarification: THREADS and MYTHREAD values are invariant
Issue #97
new
Originally reported on Google Code with ID 97
Re: the recently ratified Issue 32:
THREADS/MYTHREAD have "integral value" rather than "type int"
The current language states that THREADS is:
a value of type int}; it specifies the number of
threads and has the same value on every
thread. Under the static THREADS translation environment, {\tt THREADS}
is an integer constant suitable for use in
{\tt \#if} preprocessing directives.
Although "has the same value on every thread" might indicate that the value is constant
during the course of program execution, it does not state this directly.
The definition of MYTHREAD is:
a value of type int}; it specifies the
unique thread index.
Similarly, this definition does not explicitly state the value of MYTHREAD is invariant
when evaluated by each UPC thread.
At issue: is the specification sufficiently clear that both the THREADS and MYTHREAD
expression values are constant when evaluated (1) across all threads (for THREADS)
and (2) on each thread (for MYTHREAD)?
Reported by gary.funck
on 2012-10-14 15:52:20
Comments (4)
-
Account Deleted -
Account Deleted Reported by
danbonachea
on 2012-10-16 03:51:50 -
Account Deleted I think the proposed text is "harmless", but is also "pointless". So, my vote is for No Change.
Reported by
phhargrove@lbl.gov
on 2012-10-16 03:55:21 -
Account Deleted Gary agreed on the 11/29 telecon that this clarification is unnecessary.
Reported by
danbonachea
on 2012-11-29 19:50:06 - Status changed:Rejected
- Log in to comment
Reported by
danbonachea
on 2012-10-16 03:44:41 - Status changed:Accepted