[all-commits] [llvm/llvm-project] 673e30: [flang][runtime] Let more list-directed child inpu...

[Peter Klausler via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 673e3051b0ededcf9e028a86faae6d2ba8b09daa
      https://github.com/llvm/llvm-project/commit/673e3051b0ededcf9e028a86faae6d2ba8b09daa
  Author: Peter Klausler <pklausler at nvidia.com>
  Date:   2025-09-30 (Tue, 30 Sep 2025)

  Changed paths:
    M flang-rt/include/flang-rt/runtime/io-error.h
    M flang-rt/include/flang-rt/runtime/io-stmt.h
    M flang-rt/lib/runtime/descriptor-io.cpp
    M flang-rt/lib/runtime/edit-input.cpp
    M flang-rt/lib/runtime/io-stmt.cpp
    M flang/docs/Extensions.md

  Log Message:
  -----------
  [flang][runtime] Let more list-directed child input advance (#160590)

Whether list-directed child READ statements should be allowed to advance
to further records is neither explicit in the standard nor consistent in
existing Fortran implementations. We allow child namelist READ
statements to advance, but not other list- directed child input.

This patch refines our interpretation of this case. Child namelist READ
statements continue to be able to advance; in addition, non-namelist
child READ statements can now advance if their parent READ statement is
a list-directed input statement at the top level, or a child that could.
But non-namelist list-directed child input taking place in a context
with explicit format control won't advance to following records, so that
the format-controlled parent READ statement can retain control over
record advancement.

Also corrects two cases of record repositioning in numeric input
editing, which were failing under child input because they weren't
allowing for left tab limits.

Fixes https://github.com/llvm/llvm-project/issues/160351.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications