diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2023-02-16 10:46:50 -0800 |
|---|---|---|
| committer | Peter Klausler <pklausler@nvidia.com> | 2023-02-16 16:41:15 -0800 |
| commit | 65277494f04da7c4fd5903138d057c0faac7ba9a (patch) | |
| tree | e36fd19db7802423b47a2e011b7b360143590d9c /llvm/lib/CodeGen/CodeGen.cpp | |
| parent | 52a774fd4c18abaa9bbe23944843dbfde26c4369 (diff) | |
| download | llvm-65277494f04da7c4fd5903138d057c0faac7ba9a.zip llvm-65277494f04da7c4fd5903138d057c0faac7ba9a.tar.gz llvm-65277494f04da7c4fd5903138d057c0faac7ba9a.tar.bz2 | |
[flang][runtime] Allow record advancement in child I/O via '/' control edit descriptor
My earlier misreading of the Fortran standards had convinced me that child I/O
-- meaning the use of user-defined subroutines via generic interfaces to implement
data transfer statements -- was not allowed to advance the current record in the
ultimate unit of the original (non-child parent) data transfer statement.
This turns out to be wrong, so forward AdvanceRecord() from ChildFormattedIoStatement<>
to its parent I/O statement rather than implementing it as a no-op.
Differential Revision: https://reviews.llvm.org/D144205
Diffstat (limited to 'llvm/lib/CodeGen/CodeGen.cpp')
0 files changed, 0 insertions, 0 deletions