https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90048
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Fortran OpenACC 'private' |Fortran OpenACC 'private'
|clause rejected for |clause rejected for
|implicitly private loop |predetermined private loop
|iteration variable |iteration variable
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(Summary corrected to say "predetermined private" instead of "implicitly
private".)
OpenACC 2.6 (same in 2.7), in section 2.6.1. "Variables with Predetermined Data
Attributes" states that "The loop variable in a C 'for' statement or Fortran
'do' statement that is associated with a loop directive is predetermined to be
private to each thread that will execute each iteration of the loop. Loop
variables in Fortran 'do' statements within a compute construct are
predetermined to be private to the thread that executes the loop".
It also states in section 2.6. "Data Environment" that "Variables with
predetermined data attributes may not appear in a data clause that conflicts
with that data attribute", which can be understood to mean that such variables
may (redundantly) appear in clauses that conform with that data attribute.
