OpenMP 4.1 target task

[hahnjo]

OpenMP 4.1 will require a target task for all target constructs except #pragma omp target data.

Are there already any plans for this? Should this be implemented in libomptarget or in clang?
From what I can see, Intel introduced proxy tasks to libomp and calls the relevant functions from compiler-generated code (currently only if a nowait is present)...

I'm asking because they would be really helpful up to needed for OMPT development.

[AlexandreEichenberger]

A careful read of the specs on target, target enter/exit data, and target update show that the tasks are very unusual, compared to normal tasks. The task must execute directly, the target must be initiated directly, and then, with a nowait, the encountering thread may resume execution following the target construct.
There is still an open debate about how dependences, maps, and privates are used for such special tasks. So it will take a bit more time before things are truly sorted out (i.e. what does it mean to have first private for merged task). So the implementation may have to wait a bit on these features until there is a clear consensus in the community on the features of these tasks.
With regards to OMPT, one could generate task events for all target constructs (except the target data). Or only for the ones with dependences or nowait [but all have technically a task scheduling point inside the construct, regardless of the nowait]