This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/46321] [OOP] Polymorphic deallocation
- From: "sfilippone at uniroma2 dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 07 May 2012 09:32:30 +0000
- Subject: [Bug fortran/46321] [OOP] Polymorphic deallocation
- Auto-submitted: auto-generated
- References: <bug-46321-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321
--- Comment #5 from Salvatore Filippone <sfilippone at uniroma2 dot it> 2012-05-07 09:32:30 UTC ---
(In reply to comment #1)
> Note: There are four cases where a polymorphic deallocate is needed - though
> some might end up in the same code path:
>
> - explicit DEALLOCATE (cf. comment 0)
> - implicit deallocate at the end of the scope
> - implicit deallocate via INTENT(OUT) (cf. PR 47637)
> - implicit deallocate when doing polymorphic reallocate on assignment (PR
> 43366)
Looks to me like work on FINAL needs to be interfaced here anyway. Naive view
is that $free points to a FINAL if there is one, or to a default when there's
no FINAL, but the hookup work is the same..