Skip to content

[flang][NFC] Document ALLOCATE/DEALLOCATE error semantics #153027

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 13, 2025
Merged

[flang][NFC] Document ALLOCATE/DEALLOCATE error semantics #153027

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions flang/docs/Extensions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -900,6 +900,16 @@ print *, [(j,j=1,10)]
since these default values need to be available to process incomplete
structure constructors.

* When an `ALLOCATE` or `DEALLOCATE` statement with multiple variables
has a `STAT=` specifier that allows the program to continue execution
after an error, the variables after the one with the error are left
deallocated (or allocated). This interpretation allows the program to
identify the variable that encountered the problem while avoiding any
ambiguity in the case of multiple errors with distinct status codes.
Some compilers work differently; for maximum portability, avoid
`ALLOCATE` and `DEALLOCATE` statements with error recovery for
multiple variables.

## De Facto Standard Features

* `EXTENDS_TYPE_OF()` returns `.TRUE.` if both of its arguments have the
Expand Down
Loading