[Bug fortran/46321] [OOP] Polymorphic deallocation

2016-11-16 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 janus at gcc dot gnu.org changed: What|Removed |Added Target Milestone|--- |4.9.0

[Bug fortran/46321] [OOP] Polymorphic deallocation

2013-08-08 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 janus at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/46321] [OOP] Polymorphic deallocation

2013-07-22 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 --- Comment #7 from janus at gcc dot gnu.org --- Comment 0 has apparently been fixed by r199643. One should check whether the remaining items are also handled correctly already (in particular comments 1 - 3).

[Bug fortran/46321] [OOP] Polymorphic deallocation

2012-05-07 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 --- Comment #6 from janus at gcc dot gnu.org 2012-05-07 09:49:52 UTC --- (In reply to comment #5) > 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 whe

[Bug fortran/46321] [OOP] Polymorphic deallocation

2012-05-07 Thread sfilippone at uniroma2 dot it
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 --- Comment #5 from Salvatore Filippone 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.

[Bug fortran/46321] [OOP] Polymorphic deallocation

2012-01-29 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 --- Comment #4 from Tobias Burnus 2012-01-29 14:06:41 UTC --- Remember also to update the component handling, cf. PR 51972 comment 3.

[Bug fortran/46321] [OOP] Polymorphic deallocation

2011-11-26 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 --- Comment #3 from Tobias Burnus 2011-11-26 12:38:01 UTC --- For MOVE_ALLOC one also needs to do a polymorphic deallocation.

[Bug fortran/46321] [OOP] Polymorphic deallocation

2011-02-21 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 --- Comment #2 from janus at gcc dot gnu.org 2011-02-21 15:06:10 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 (

[Bug fortran/46321] [OOP] Polymorphic deallocation

2011-02-09 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 --- Comment #1 from Tobias Burnus 2011-02-09 13:59:09 UTC --- 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 th

[Bug fortran/46321] [OOP] Polymorphic deallocation

2010-11-05 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46321 Tobias Burnus changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|