http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48700
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.05.15 10:30:25
CC| |janus at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #1 from janus at gcc dot gnu.org 2011-05-15 10:30:25 UTC ---
(In reply to comment #0)
> ==25909== 40 bytes in 1 blocks are definitely lost in loss record 3 of 4
> ==25909== at 0x4A05E46: malloc (vg_replace_malloc.c:195)
> ==25909== by 0x401425: MAIN__ (testmv3.f90:37)
> ==25909== by 0x401729: main (testmv3.f90:22)
This guy is due to polymorphic deallocation not working properly yet (cf.
PR46321), it is unrelated to MOVE_ALLOC. The component "ka", which is allocated
by "sm%ka=dat%sm%ja", is never freed. We presently only free the components of
the declared type, not the dynamic type.
