aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorRazvan Lupusoru <razvan.lupusoru@gmail.com>2025-07-29 10:03:22 -0700
committerGitHub <noreply@github.com>2025-07-29 10:03:22 -0700
commit4128cf3b26cff997f1f315ee571cbc7110bc250c (patch)
tree6462d3ed1b651e720ea34eeefdfecaf3c549cf14 /lldb/packages/Python/lldbsuite/test
parent2a3f72ee6e435382dd5bc46f2961c3698ac20eec (diff)
downloadllvm-4128cf3b26cff997f1f315ee571cbc7110bc250c.zip
llvm-4128cf3b26cff997f1f315ee571cbc7110bc250c.tar.gz
llvm-4128cf3b26cff997f1f315ee571cbc7110bc250c.tar.bz2
[flang][acc] Lower do and do concurrent loops specially in acc regions (#149614)
When OpenACC is enabled and Fortran loops are annotated with `acc loop`, they are lowered to `acc.loop` operation. And rest of the contained loops use the normal FIR lowering path. Hovever, the OpenACC specification has special provisions related to contained loops and their induction variable. In order to adhere to this, we convert all valid contained loops to `acc.loop` in order to store this information appropriately. The provisions in the spec that motivated this change (line numbers are from OpenACC 3.4): - 1353 Loop variables in Fortran do statements within a compute construct are predetermined to be private to the thread that executes the loop. - 3783 When do concurrent appears without a loop construct in a kernels construct it is treated as if it is annotated with loop auto. If it appears in a parallel construct or an accelerator routine then it is treated as if it is annotated with loop independent. By valid loops - we convert do loops and do concurrent loops which have induction variable. Loops which are unstructured are not handled.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions