[gomp4.1] Initial support for some OpenMP 4.1 construct parsing

Ilya Verbin iverbin@gmail.com
Tue Jun 9 18:39:00 GMT 2015


On Wed, Apr 29, 2015 at 14:06:44 +0200, Jakub Jelinek wrote:
> [...] The draft requires only alloc or to
> (or always, variants) for enter data and only from or delete (or always,
> variants) for exit data, so in theory it is possible to figure that from
> the call without extra args, but not so for update - enter data is supposed
> to increment reference counts, exit data decrement. [...]

TR3.pdf also says about 'release' map-type for exit data, but it is not
described in the document.

> [...] And, we'll need new
> arguments for async (pass through info that it is async (nowait) or sync,
> and the depend clause address(es)).

I don't quite understand from "If a depend clause is present, then it is treated
as if it had appeared on the implicit task construct that encloses the target
construct", is

  #pragma omp target depend(inout: x)

equivalent to

  #pragma omp task depend(inout: x)
  #pragma omp target

or not?

In other words, can't we just generate GOMP_task (...) with GOMP_target (...)
inside, without any new arguments?

Thanks,
  -- Ilya



More information about the Gcc-patches mailing list