diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2022-04-04 06:44:05 -0700 |
|---|---|---|
| committer | Peter Klausler <pklausler@nvidia.com> | 2022-04-14 13:56:04 -0700 |
| commit | eb14135e35bf2463a5c52394f311d47c18d72dee (patch) | |
| tree | dbe0a22aa62ee90d082c987392db539117d8af12 /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp | |
| parent | 753aabeaae6547975e7212d38100e9c6201c0aa5 (diff) | |
| download | llvm-eb14135e35bf2463a5c52394f311d47c18d72dee.zip llvm-eb14135e35bf2463a5c52394f311d47c18d72dee.tar.gz llvm-eb14135e35bf2463a5c52394f311d47c18d72dee.tar.bz2 | |
[flang] Correct interaction between generics and intrinsics
Fortran allows a generic interface to have he same name as an
intrinsic procedure. If the intrinsic is explicitly marked with
the INTRINSIC attribute, restrictions apply (C848) - the generic
must contain only functions or subroutines, depending on the
intrinsic. Explicit or not, the generic overrides the intrinsic,
but the intrinsic behavior must still be available for calls
whose actual arguments do not match any of the specific procedures.
Semantics was not checking constraint C848, and it didn't allow
an explicit INTRINSIC attribute on a name of a generic interface.
Differential Revision: https://reviews.llvm.org/D123713
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions