Taken from my remark to PR31320,
http://gcc.gnu.org/ml/gcc-patches/2007-07/msg01457.html
The generated executable leaks memory:
96 bytes in 1 blocks are definitely lost in loss record 1 of 2
at 0x4C22D06: malloc (in
/usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
by 0x40122B: MAIN__ (alloc_comp_assign_2.f90:11)
by 0x401EEB: main (fmain.c:22)
96 bytes in 1 blocks are definitely lost in loss record 2 of 2
at 0x4C22D06: malloc (in
/usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
by 0x400BCA: MAIN__ (alloc_comp_assign_2.f90:10)
by 0x401EEB: main (fmain.c:22)
for this stripped down test case
type :: a
integer, allocatable :: i(:)
end type a
type :: b
type (a), allocatable :: at(:)
end type b
type(a) :: x(2)
type(b) :: y(2)
integer i
y(1) = b ((/x(1),x(2)/))
y(2) = b ((/x(2),x(1)/))
forall (i=1:2) y(i) = b ((/x(i)/))
end
Paul remarked:
The testcase that you sent me breaks gfortran in other places and probably
should have a PR all of its very own. (try the FORALL part separately).
--
Summary: Leaking memory (generated prog) with type constructor &
allocatable components
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: burnus at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32795
