http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45827
--- Comment #27 from Mikael Morin <mikael at gcc dot gnu.org> 2010-10-24 15:48:27 UTC --- (In reply to comment #26) > I did not see any reply to my comment #19. Isn't it obvious there is > something > wromg at that point in the module.c ? No, it's unreleased memory; it's harmless. Valgrind shows these _warnings_ with the --leak-check=full argument if one wants to track unfreed pointers. It means that gfortran could be improved to save a few kBs of memory, but not that we are using uninitialized data, writing to random unallocated places or doing whatever deserving an _error_. What's important is "0 errors from 0 contexts" in the summary at the end. Note that sometimes fixing a warning exposes genuine errors, so it's not just as simple as that. > Did I miss something in the thread here? What _I_ miss is a code to reproduce the error. :-(
