aboutsummaryrefslogtreecommitdiff
path: root/lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp
diff options
context:
space:
mode:
authorPeter Klausler <pklausler@nvidia.com>2023-05-18 10:32:14 -0700
committerPeter Klausler <pklausler@nvidia.com>2023-05-22 12:03:36 -0700
commit3d05ab6d3e24e76ff53b8d7d623c436b4be5b809 (patch)
tree4541609b0fa11e97f3197165f8ccaed8f489b599 /lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp
parenta8654b44579d35ffaed0634eaf76cbceae6748f1 (diff)
downloadllvm-3d05ab6d3e24e76ff53b8d7d623c436b4be5b809.zip
llvm-3d05ab6d3e24e76ff53b8d7d623c436b4be5b809.tar.gz
llvm-3d05ab6d3e24e76ff53b8d7d623c436b4be5b809.tar.bz2
[flang] Better error handling and testing of generics with homonymous specifics or derived types
Fortran allows a generic procedure interface to have the same name as a derived type in the same scope or the same name as one of its specific procedures. (It can't have both since a derived type and specific procedure can't have the same name in a scope.) Some popular compilers allow generic interfaces with distinct accessible homonymous specific procedures to be merged by USE association. Thsi compiler does not, and for good reason: it leads to ambiguity in cases where a procedure name appears outside a reference, such as in a PROCEDURE declaration statement as the procedure's interface, the target of a procedure pointer assignment statement, or as an actual argument. This patch cleans up the code that handles these cases, improves some error messages, and adds more tests. Resolves https://github.com/llvm/llvm-project/issues/60228. Differential Revision: https://reviews.llvm.org/D150915
Diffstat (limited to 'lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp')
0 files changed, 0 insertions, 0 deletions