[all-commits] [llvm/llvm-project] 4859b9: [flang][acc] Update FIR ref, heap, and pointer to ...

[Razvan Lupusoru via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 4859b92b7f4e0365517acd464cec29721f469461
      https://github.com/llvm/llvm-project/commit/4859b92b7f4e0365517acd464cec29721f469461
  Author: Razvan Lupusoru <razvan.lupusoru at gmail.com>
  Date:   2025-07-10 (Thu, 10 Jul 2025)

  Changed paths:
    M flang/lib/Lower/OpenACC.cpp
    M flang/lib/Optimizer/Dialect/FIRType.cpp
    M flang/lib/Optimizer/OpenACC/FIROpenACCTypeInterfaces.cpp
    M flang/lib/Optimizer/OpenACC/RegisterOpenACCExtensions.cpp
    M flang/test/Fir/OpenACC/openacc-mappable.fir
    M flang/test/Fir/OpenACC/openacc-type-categories-class.f90
    M flang/test/Fir/OpenACC/openacc-type-categories.f90
    M flang/test/lib/OpenACC/TestOpenACCInterfaces.cpp
    M mlir/lib/Dialect/OpenACC/IR/OpenACC.cpp

  Log Message:
  -----------
  [flang][acc] Update FIR ref, heap, and pointer to be MappableType (#147834)

The MappableType OpenACC type interface is a richer interface that
allows OpenACC dialect to be capable to better interact with a source
dialect, FIR in this case. fir.box and fir.class types already
implemented this interface. Now the same is being done with the other
FIR types that represent variables.

One additional notable change is that fir.array no longer implements
this interface. This is because MappableType is primarily intended for
variables - and FIR variables of this type have storage associated and
thus there's a pointer-like type (fir.ref/heap/pointer) that holds the
array type.

The end goal of promoting these FIR types to MappableType is that we
will soon implement ability to generate recipes outside of the frontend
via this interface.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications