https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61628
--- Comment #10 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- Just to be sure I am using the right file, its md5 signature is MD5 (binary_data) = 681215e5351ab45a494c044719776690 I am also attaching the output file which looks OK, but a double check does not hurt. Valgrind reports a quite large memory leak: ==2066== HEAP SUMMARY: ==2066== in use at exit: 1,302,891 bytes in 383 blocks ==2066== total heap usage: 501 allocs, 118 frees, 11,311,380 bytes allocated ==2066== ==2066== 1,277,556 bytes in 1 blocks are definitely lost in loss record 77 of 77 ==2066== at 0x7011: malloc (vg_replace_malloc.c:295) ==2066== by 0x10000087F: MAIN__ (pr61628.f90:13) ==2066== by 0x100000D08: main (pr61628.f90:25) ==2066== ==2066== LEAK SUMMARY: ==2066== definitely lost: 1,277,556 bytes in 1 blocks ==2066== indirectly lost: 0 bytes in 0 blocks ==2066== possibly lost: 0 bytes in 0 blocks ==2066== still reachable: 0 bytes in 0 blocks ==2066== suppressed: 25,335 bytes in 382 blocks ==2066== ==2066== For counts of detected and suppressed errors, rerun with: -v ==2066== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4934 from 60)
