https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68927
Thomas Koenig changed:
What|Removed |Added
Status|WAITING |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68927
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68927
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68927
--- Comment #3 from Bill Long ---
Possibly related to pr59796, bun not a duplicate. In this example, the pointer
being deallocated is associated. The problem is that it is associated with a
target that cannot be deallocated. The standard says
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68927
--- Comment #1 from Bill Long ---
The DEALLOCATE statement in subroutine SUB is attempting to deallocate
a static array with the SAVE attribute. The standard requires that a
non-zero status be returned in cases like this, and execution
