[llvm-bugs] [Bug 49240] New: target update beyond range should stop instead of noop

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=49240

            Bug ID: 49240
           Summary: target update beyond range should stop instead of noop
           Product: OpenMP
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Runtime Library
          Assignee: unassignedbugs at nondot.org
          Reporter: xw111luoye at gmail.com
                CC: llvm-bugs at lists.llvm.org

The runtime should stop for the following code, instead of treating the
transfer as no-op and running through.

int main()
{
  int a[10];
  #pragma omp target enter data map(alloc: a[:10])
  #pragma omp target update to(a[:20])
  #pragma omp target exit data map(delete: a[:10])
}

Libomptarget --> Looking up mapping(HstPtrBegin=0x00007ffe3fe353f0, Size=80)...
Libomptarget --> WARNING: Pointer is already mapped but section extends beyond
mapped region
Libomptarget --> hst data:0x00007ffe3fe353f0 not found, becomes a noop

Let me know if the OpenMP specification explicitly says this is the intended
behavior.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20210218/2b993ffe/attachment.html>