[all-commits] [llvm/llvm-project] cbcb7a: [mlir][acc] Introduce MappableType interface (#122...
Razvan Lupusoru via All-commits
all-commits at lists.llvm.org
Thu Jan 9 10:27:59 PST 2025
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: cbcb7ad32e6faca1f4c0f2f436e6076774104e17
https://github.com/llvm/llvm-project/commit/cbcb7ad32e6faca1f4c0f2f436e6076774104e17
Author: Razvan Lupusoru <razvan.lupusoru at gmail.com>
Date: 2025-01-09 (Thu, 09 Jan 2025)
Changed paths:
M mlir/docs/Dialects/OpenACCDialect.md
M mlir/include/mlir/Dialect/OpenACC/OpenACC.h
M mlir/include/mlir/Dialect/OpenACC/OpenACCOps.td
M mlir/include/mlir/Dialect/OpenACC/OpenACCTypeInterfaces.td
M mlir/lib/Dialect/OpenACC/IR/OpenACC.cpp
M mlir/unittests/Dialect/OpenACC/OpenACCOpsTest.cpp
Log Message:
-----------
[mlir][acc] Introduce MappableType interface (#122146)
OpenACC data clause operations previously required that the variable
operand implemented PointerLikeType interface. This was a reasonable
constraint because the dialects currently mixed with `acc` do use
pointers to represent variables. However, this forces the "pointer"
abstraction to be exposed too early and some cases are not cleanly
representable through this approach (more specifically FIR's `fix.box`
abstraction).
Thus, relax this by allowing a variable to be a type which implements
either `PointerLikeType` interface or `MappableType` interface.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list