https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87270
Paul Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87270
--- Comment #6 from anlauf at gcc dot gnu.org ---
All current compilers seem to give the same, apparently correct result,
even with different optimization level.
So can we close this finally?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87270
--- Comment #5 from paul.richard.thomas at gmail dot com ---
Hi Janus,
That's wierd. I don't see any final call output with any of the
branches, going back to 6-branch.
I am also puzzled by the lack of calls, given that the finalization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87270
--- Comment #4 from janus at gcc dot gnu.org ---
(In reply to Paul Thomas from comment #3)
> It seems that finalization has never occurred with any branch for this case,
I don't fully agree with this statement.
Apart from the fact that gfortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87270
--- Comment #3 from Paul Thomas ---
(In reply to janus from comment #2)
> (In reply to Dominique d'Humieres from comment #1)
> > This seems to have been fixed by revision r264008 on trunk
>
> Seems the segfault is 'fixed' due to the fact that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87270
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87270
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
