diff options
author | Peter Klausler <pklausler@nvidia.com> | 2025-10-03 10:48:13 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-10-03 10:48:13 -0700 |
commit | cbe3b72c4c9378c9e4f2fd1b5e4d0f9e63d8f6bb (patch) | |
tree | fd671ef51232481091af2f094517ec5a878eaaef /libcxx/include/__algorithm/comp.h | |
parent | 1fba01a51d6cbf1cc63f4209203babd81950c5e6 (diff) | |
download | llvm-cbe3b72c4c9378c9e4f2fd1b5e4d0f9e63d8f6bb.zip llvm-cbe3b72c4c9378c9e4f2fd1b5e4d0f9e63d8f6bb.tar.gz llvm-cbe3b72c4c9378c9e4f2fd1b5e4d0f9e63d8f6bb.tar.bz2 |
[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.
Diffstat (limited to 'libcxx/include/__algorithm/comp.h')
0 files changed, 0 insertions, 0 deletions