[all-commits] [llvm/llvm-project] cbe3b7: [flang][CUDA] Downgrade error to warning (#161570)

[Peter Klausler via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: cbe3b72c4c9378c9e4f2fd1b5e4d0f9e63d8f6bb
      https://github.com/llvm/llvm-project/commit/cbe3b72c4c9378c9e4f2fd1b5e4d0f9e63d8f6bb
  Author: Peter Klausler <pklausler at nvidia.com>
  Date:   2025-10-03 (Fri, 03 Oct 2025)

  Changed paths:
    M flang/include/flang/Evaluate/characteristics.h
    M flang/lib/Evaluate/characteristics.cpp
    M flang/lib/Semantics/check-call.cpp
    M flang/lib/Semantics/expression.cpp
    M flang/test/Semantics/boz-literal-constants.f90
    M flang/test/Semantics/call13.f90
    A flang/test/Semantics/cuf24.cuf
    M flang/test/Semantics/null01.f90

  Log Message:
  -----------
  [flang][CUDA] Downgrade error to warning (#161570)

The compiler currently emit an error about the lack of an explicit
procedure interface when an external procedure that is called via an
implicit interface is known to have an dummy argument with a CUDA data
attribute, even when the corresponding actual argument does have a CUDA
data attribute. This behavior is inconsistent with what happens when
such a call is to an external in another source file and its definition
is not visible -- the compiler silently accepts an actual argument with
a CUDA data attribute across the implicit interface.

Harmonize this situation so that an actual argument with a CUDA data
attribute in a reference to a procedure with an implicit interface
elicits a usage warning encouraging the use of explicit interfaces. Only
when the procedure's definition is visible, and incompatible, will an
error message appear.



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