https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94109
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|WAITING |RESOLVED
--- Comment #21 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Unfortunately, there isn't going to be any more release for gcc 7.
I could backport this to the gcc-7 branch, but the likelyhood
that distributions would pick it up from the branch is almost nil.
As for a workaround for memory leaks, you can always add
if (.not. allocated(a)) deallocate (a)
to your source code. It's not what allocatables are about,
but it would work.
Thanks for reporting this, and for reducing the two test cases!
I'm closing this as fixed for now.
