[Openmp-commits] [flang] [mlir] [openmp] [Flang][OpenMP] Initial mapping of Fortran pointers and allocatables for target devices (PR #71766)

via Openmp-commits openmp-commits at lists.llvm.org
Wed Dec 6 04:01:43 PST 2023

@@ -0,0 +1,27 @@
+! Offloading test checking interaction of a
+! non-array allocatable with a target region
+! REQUIRES: flang, amdgcn-amd-amdhsa
+! UNSUPPORTED: nvptx64-nvidia-cuda
+! UNSUPPORTED: nvptx64-nvidia-cuda-LTO
+! UNSUPPORTED: aarch64-unknown-linux-gnu
+! UNSUPPORTED: aarch64-unknown-linux-gnu-LTO
+! UNSUPPORTED: x86_64-pc-linux-gnu
+! UNSUPPORTED: x86_64-pc-linux-gnu-LTO
+! RUN: %libomptarget-compile-fortran-run-and-check-generic
+! XFAIL: *
+program main
+    integer, allocatable :: test
+    allocate(test)
+    test = 10
+!$omp target map(tofrom:test)
+    test = 50
agozillon wrote:

Yes, unfortunately the OpenMP offload flow didn't cover this at the time, and there's likely a lot of cases it doesn't cover just now that we may encounter similar issues in the future. 

I'm happy to create a ticket and try to open it up for discussion in a future call, is there a particular call you'd recommend e.g. the Bi-weekly Flang call or one of the OpenMP Bi-weekly's? And how I'd get it on the agenda for discussion (some I know how to do so, others like the Bi-weekly Flang call not so much unfortunately).


More information about the Openmp-commits mailing list