[flang][cuda] Only transfer component in implicit data transfer (#242061)

When the right-hand side of a host assignment references a CUDA device
component, such as `out = m(1)%d(1) + h` with `d` a device allocatable
component of a managed `m`, genCUDAImplicitDataTransfer collected both
the
component and the object it is taken from. The base has no device
address
to transfer, so lowering hit `dyn_cast on a non-existent value` for
dummy
arguments, and a managed base could be transferred a second time.

The attribute of a component hides the one of its base, which is the
rule
IsCUDADataTransfer already applies. Collect the effective CUDA symbols
so a
component masks its base, and lower the component reference itself:
component symbols have no address, so the designator is lowered, copied
to
a temporary, and the temporary is registered as a component override for
the rest of the assignment. The null getDefiningOp() is also guarded.

Add convertDataRefToHLFIRVariable to lower a DataRef to its HLFIR
variable.
6 files changed
tree: d0cfc0de2dfc4bfe97777f943bfa6a131963fa04
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. flang-rt/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libsycl/
  16. libunwind/
  17. lld/
  18. lldb/
  19. llvm/
  20. llvm-libgcc/
  21. mlir/
  22. offload/
  23. openmp/
  24. orc-rt/
  25. polly/
  26. runtimes/
  27. third-party/
  28. utils/
  29. .clang-format
  30. .clang-format-ignore
  31. .clang-tidy
  32. .git-blame-ignore-revs
  33. .gitattributes
  34. .gitignore
  35. .mailmap
  36. CODE_OF_CONDUCT.md
  37. CONTRIBUTING.md
  38. LICENSE.TXT
  39. pyproject.toml
  40. README.md
  41. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

Welcome to the LLVM project!

This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.

The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.

C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.

Other components include: the libc++ C++ standard library, the LLD linker, and more.

Getting the Source Code and Building LLVM

Consult the Getting Started with LLVM page for information on building and running LLVM.

For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.

Getting in touch

Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.

The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.