------- Comment #2 from zsojka at seznam dot cz 2010-03-13 09:19 ------- Thank you for feedback. However, this happens in r157335, so it's not fixed by that patch. It's only reproducible with valgrind checking because ggc_alloc_stat() uses VALGRIND_DISCARD which is a no-op in other cases. When valgrind checking is enabled, it marks memory as uninitialised, even when malloc() isn't used to allocate it (some custom memory allocation is done). That's why "Uninitialised value was created by a client request" is printed in the "where does uninitialised memory come from?" part of the message.
I don't know if this is a real issue, or the result doesn't depend on this uninitialised read (because further test it the condition will be false anyway). -- zsojka at seznam dot cz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|DUPLICATE | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43332