diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2023-02-28 11:58:30 -0800 |
|---|---|---|
| committer | Peter Klausler <pklausler@nvidia.com> | 2023-03-02 10:10:06 -0800 |
| commit | 69e2665c8bcf210d0cb864b86f79747af1432642 (patch) | |
| tree | edb8fddf1143ed908816e4995f7992e27b3feaf9 /lldb/test/API/python_api/debugger/TestDebuggerAPI.py | |
| parent | 33cf40122279342b50f92a3a53f5c185390b6018 (diff) | |
[flang] BIND(C,NAME=...) corrections
The Fortran standard's various restrictions on the use of BIND(C)
often depend more on the presence or absence of an explicit NAME=
specification rather than on its value, but semantics and module
file generation aren't making distinctions between explicit NAME=
specifications that happen to match the default name and declarations
that don't have NAME=. Tweak semantics and module file generation
to conform, and also complain when named BIND(C) attributes are
erroneously applied to entities that can't support them, like
ABSTRACT interfaces.
Differential Revision: https://reviews.llvm.org/D145107
Diffstat (limited to 'lldb/test/API/python_api/debugger/TestDebuggerAPI.py')
0 files changed, 0 insertions, 0 deletions