diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2023-04-13 10:28:19 -0700 |
|---|---|---|
| committer | Peter Klausler <pklausler@nvidia.com> | 2023-04-13 15:35:01 -0700 |
| commit | 7cf1608b4d8f7f4d20c994dd13451efb7c9560b5 (patch) | |
| tree | b515cb2dd847a699960ea3afdc64b2514000a0f0 /lldb/test/Shell/ScriptInterpreter/Python | |
| parent | 3ece37b3fa2c14157ad02967b867570c6a0c08e8 (diff) | |
| download | llvm-7cf1608b4d8f7f4d20c994dd13451efb7c9560b5.zip llvm-7cf1608b4d8f7f4d20c994dd13451efb7c9560b5.tar.gz llvm-7cf1608b4d8f7f4d20c994dd13451efb7c9560b5.tar.bz2 | |
[flang] Rework handling of non-type-bound user-defined I/O
A fairly recent introduction of runtime I/O APIs called OutputDerivedType()
and InputDerivedType() didn't cover NAMELIST I/O's need to access
non-type-bound generic interfaces for user-defined derived type I/O
when those generic interfaces are defined in some scope other than the
one that defines the derived type.
The patch adds a new data structure shared between lowering
and the runtime that can represent all of the cases that can
arise with non-type-bound defined I/O. It can represent
scopes in which non-type-bound defined I/O generic interfaces
are inaccessible, too, due to IMPORT statements.
The data structure is now an operand to OutputDerivedType() and
InputDerivedType() as well as a data member in the NamelistGroup
structure.
Differential Revision: https://reviews.llvm.org/D148257
Diffstat (limited to 'lldb/test/Shell/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions
