------- Comment #12 from burnus at gcc dot gnu dot org 2008-02-07 22:17 ------- > This is regtesting but all the allocatable component tests are OK. > Could somebody check the memory leakage for me, please? The test of comment 2 > is now OK in that it prints the right numbers.
Thanks for the wrong-code fix; valgrind also shows no invalid accesses etc. However, the initial bug of comment 0 is still present: As valgrind --leak-check=full shows, the generated program still leaks memory: ==19078== 96 bytes in 1 blocks are definitely lost in loss record 1 of 2 ==19078== at 0x4C2560E: malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so) ==19078== by 0x401246: MAIN__ (dfdf.f90:11) ==19078== by 0x401FDB: main (fmain.c:21) ==19078== ==19078== ==19078== 96 bytes in 1 blocks are definitely lost in loss record 2 of 2 ==19078== at 0x4C2560E: malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so) ==19078== by 0x400B52: MAIN__ (dfdf.f90:10) ==19078== by 0x401FDB: main (fmain.c:21) I think the one-liner could go into GCC 4.3.0 as it fixes a (user-visible) wrong-code bug; still the missing _builtin_free calls should be added later. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32795
