This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns
- From: "zsojka at seznam dot cz" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Mar 2010 09:19:48 -0000
- Subject: [Bug rtl-optimization/43332] valgrind warns about using uninitialized variable with -fsched-pressure -fschedule-insns
- References: <bug-43332-14164@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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