https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80524
Paul Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80524
--- Comment #9 from CVS Commits ---
The master branch has been updated by Paul Thomas :
https://gcc.gnu.org/g:d7caf313525a46f200d7f5db1ba893f853774aee
commit r13-6747-gd7caf313525a46f200d7f5db1ba893f853774aee
Author: Paul Thomas
Date: Sat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80524
Paul Thomas changed:
What|Removed |Added
CC||pault at gcc dot gnu.org
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80524
--- Comment #7 from Jürgen Reuter ---
This is still present in the actual trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80524
--- Comment #6 from Andrew Wood ---
For info, the actual code I was developing did use the finalization subroutine
to deallocate pointers, which resulted in seg faults when compiled with ifort.
This was how I discovered the problem.
I also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80524
--- Comment #5 from Jerry DeLisle ---
(In reply to janus from comment #4)
> (In reply to Jerry DeLisle from comment #3)
> > I think this depends a lot on the compiler implementation.
>
> I don't actually think the calling of finalization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80524
--- Comment #4 from janus at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #3)
> I think this depends a lot on the compiler implementation.
I don't actually think the calling of finalization routines is supposed to
depend on the
