Skip to content

Conversation

@klausler
Copy link
Contributor

NAMELIST input in child I/O is rare, and it's not clear in the standard whether it should be allowed to advance to later records in the parent unit. But GNU Fortran supports it, and there's no good reason not to do so since a NAMELIST input group that isn't terminated on the same line is otherwise going to be a fatal error.

Fixes #153416.

NAMELIST input in child I/O is rare, and it's not clear in the
standard whether it should be allowed to advance to later records
in the parent unit.  But GNU Fortran supports it, and there's no
good reason not to do so since a NAMELIST input group that isn't
terminated on the same line is otherwise going to be a fatal error.

Fixes llvm#153416.
@klausler klausler requested a review from DanielCChen August 16, 2025 16:27
Copy link
Contributor

@DanielCChen DanielCChen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
Thanks.

@klausler klausler merged commit 9a7a16c into llvm:main Aug 18, 2025
10 checks passed
@klausler klausler deleted the bug153416 branch August 18, 2025 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[flang][NML] Flang failed reading nested namelist

2 participants