[Openmp-commits] [PATCH] D86781: [LIBOMPTARGET]Do not try to optimize bases for the next parameters.

Shilei Tian via Phabricator via Openmp-commits openmp-commits at lists.llvm.org
Sat Aug 29 17:57:59 PDT 2020

tianshilei1992 added inline comments.

Comment at: openmp/libomptarget/src/omptarget.cpp:1068
+      const bool IsFirstPrivate =
+          (I >= ArgNum - 1 || !(ArgTypes[I + 1] & OMP_TGT_MAPTYPE_MEMBER_OF));
       Ret = PrivateArgumentManager.addArg(HstPtrBegin, ArgSizes[I],
I have a quick question: Does front end order all arguments? For example, let's say a user write the following code:
#pragma omp target first private(a.p1[0:N], b, a.p2[0:N], c, a.p3[0:N])
where `p1`, `p2` and `p3` are members of a struct `a`. Then when passing to the runtime library, `Args[I]`, `Args[I+1]` and `Args[I+2]` should be corresponding to `a.p1[0:N]`, `a.p2[0:N]`, `a.p3[0:N]`, right? They'll not be interleaved by `b` and `c`.

Comment at: openmp/libomptarget/test/mapping/lambda_mapping.cpp:10
+template <typename LOOP_BODY>
+inline void forall(int Begin, int End, LOOP_BODY LoopBody) {
+#pragma omp target parallel for schedule(static)
Really interesting fix. I didn't realize that lambda function is captured as a first-private argument.

  rG LLVM Github Monorepo



More information about the Openmp-commits mailing list