[cfe-dev] Discussion about OpenMP 5.0 declare mapper runtime

[Jon Chesterfield via cfe-dev]

>
>
> I would like to bring your attention to the choice of 2 proposals for the
> declare mapper runtime interface:
>
> 1. The current design which creates new runtime functions for declare
> mappers. For example, right now we have `__tgt_target_teams(...)` which
> corresponds to the runtime interface for `omp target teams`. Now we add
> `__tgt_target_teams_mapper(..., void **mappers)` to replace it.
>

New feature, new library call seems reasonable. The current interface can
presumably be reimplemented as a call to (the internals of) the proposed
interface.


> 2. Introduce a function `__tgt_push_mappers`, which should be called before
> every target function call (e.g., `__tgt_target_teams`) to pass the mapper
> argument for that function. The call of `__tgt_push_mappers` is implicitly
> bonded with the actual target call.
>

This seems error prone to use and likely to degrade performance.

Choice 1 seems more appealing to me.

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20191001/3b22811a/attachment.html>