Valgrind gives this: ==28681== ==28681== 25,120 (14,664 direct, 10,456 indirect) bytes in 325 blocks are definitely lost in loss record 8 of 10 ==28681== at 0x4A05996: malloc (vg_replace_malloc.c:149) ==28681== by 0xB26057: xmalloc (xmalloc.c:147) ==28681== by 0x445B04: gfc_getmem (misc.c:37) ==28681== by 0x46FB99: gfc_get_namespace (symbol.c:2079) ==28681== by 0x452A43: parse_contained (parse.c:2898) ==28681== by 0x453641: gfc_parse_file (parse.c:3205) ==28681== by 0x47AF74: gfc_be_parse_file (f95-lang.c:258) ==28681== by 0x6E9181: toplev_main (toplev.c:1042) ==28681== by 0x370C61DAB3: (below main) (in /lib64/libc-2.6.so) ==28681==
With argument_checking_8.f90 See: http://gcc.gnu.org/ml/fortran/2007-10/msg00296.html For the test case, need associated patch to see this. Memory issue is unrelated to the patch for PR31306. -- Summary: Namespace memory cleanup needed Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33845