[PATCH] D99689: [OPENMP]Add option -fopenmp-cuda-const-firstprivate to control address space of the corresponding global.

Johannes Doerfert via Phabricator via cfe-commits cfe-commits at lists.llvm.org
Wed Mar 31 19:40:45 PDT 2021


jdoerfert added a comment.

In D99689#2662852 <https://reviews.llvm.org/D99689#2662852>, @ABataev wrote:

> In D99689#2662848 <https://reviews.llvm.org/D99689#2662848>, @jdoerfert wrote:
>
>> Can you please show me a test case or explain to me when/how this global is actually used.
>
> It is passed as an argument to the target region. When libomptarget requests the memory for the firstprivate, it returns the pointer to this const global, which then passed as argument to the kernel.

So if we use it, why would we disable it?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D99689/new/

https://reviews.llvm.org/D99689



More information about the cfe-commits mailing list