http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56596
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2013-06-27
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I no longer see the valgrind error at revision 200078 (clean tree). Can this be
confirmed?
On my working tree (r200429, several patches) using valgrind with
--leak-check=full gives
==85435== 80 bytes in 1 blocks are definitely lost in loss record 1 of 2
==85435== at 0x100013679: malloc (vg_replace_malloc.c:266)
==85435== by 0x100001358: __realloc_MOD_reallocate (class_array_7.f03:31)
==85435== by 0x1000019C6: MAIN__ (class_array_7.f03:55)
==85435== by 0x100001B5B: main (class_array_7.f03:49)
(no error without --leak-check=full). Investigating.
