https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96668
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #3 from kargl at gcc dot gnu.org ---
(In reply to Tobias Burnus from comment #0)
> The exact behaviour is not well specified in OpenMP 4.5 or 5.0 but at least
> with 'always' the following is expected to map.
> (See OpenMP Issue 2152 + upcoming OpenMP TR9 – which require the always
> modifier. There is code which expects that implicit mapping and mapping
> without always modifier also works.)
>
> For pointers, at least OpenMP 5.0 seems to require that the POINTER target
> is automatically mapped:
>
> module m
> implicit none
> integer, pointer :: p1 => null()
> integer, pointer :: p1 => null()
> integer, allocatable :: a1, a2(:)
> !$omp declare target(p1, p2, a1, a2)
> end module m
>
Module m looks wrong. Should the 2nd p1 be p2?
