https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90742
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-06-06
Ever confirmed|0 |1
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Jakub, is my understanding correct, that when a Fortran 'allocatable' is used
in a 'firstprivate' clause on an OpenMP 'target' construct, then that should do
"the obvious" thing? (But it currently isn't.) That is, behave similar as a
Fortran 'allocatable' used in a 'map' clause. (Which does work as expected.)
I do note that OpenMP 5.0 doesn't seem to contain any words on this
specifically (in contrast to 'allocatable' with a 'map' clause; see 2.19.7.1
"'map' Clause", near the end), but I suppose (!) that's just because a
'firstprivate' clause need not be concerned about the case of "exit from the
region". (Relate to how 2.19.4.5 "'lastprivate' Clause" in turn *does* talk
about 'allocatable' in context of "exit from [...]".)
(..., and then similarly also for a 'private' clause, as much as applicable,
which I have not yet checked.)
Cesar's patch "[OpenACC] Add support for firstprivate Fortran allocatable
scalars" (see link above) would fix at least some aspects of this (for OpenACC
only).
Also, so far, I only consider scalars.
