https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63640
Mikael Morin changed:
What|Removed |Added
CC||mikael at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63640
janus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
Status|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63640
--- Comment #4 from Joost VandeVondele
---
(In reply to Dominique d'Humieres from comment #3)
> Is this PR INVALID?
seems more like an enhancement request to free allocatables at the end of main.
I guess this is not mandated by the standard, bu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63640
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63640
patnel97269-gfortran at yahoo dot fr changed:
What|Removed |Added
Severity|critical|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63640
--- Comment #2 from patnel97269-gfortran at yahoo dot fr ---
Thanks for the tip and the comment.
So the standard say that move_alloc deallocate the array "from". Does that mean
that the compiler mark the array as not allocated but does not free t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63640
Joost VandeVondele changed:
What|Removed |Added
CC||Joost.VandeVondele at mat dot
ethz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63640
patnel97269-gfortran at yahoo dot fr changed:
What|Removed |Added
Severity|major |critical
