[Bug middle-end/78454] valgrind conditional jump or move depends on uninitialised value(s) in sparseset_bit_p

2016-11-21 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78454

Martin Sebor  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Martin Sebor  ---
As suggested in comment #1, configuring GCC with --enable-valgrind-annotations
is needed.  Unfortunately, after that, a build fails with the errors below:

checking for valgrind.h... no
checking for VALGRIND_DISCARD in ... no
checking for VALGRIND_DISCARD in ... no
configure: error: *** Can't find valgrind/memcheck.h, memcheck.h or valgrind.h
Makefile:4286: recipe for target 'configure-stage1-gcc' failed
make[1]: *** [configure-stage1-gcc] Error 1

It seems that valgrind-devel needs to be installed in order for this to work
(it would be nice if the top-level configure warned or failed when it isn't).

With these problems out of the way though, the Valgrind errors disappear. 
Reverting r190503 brings them back, so it did indeed fix the referenced bug
54689.  I'm going to resolve this bug as a duplicate of the older one.  I've
also updated the Debugging GCC Wiki page
(https://gcc.gnu.org/wiki/DebuggingGCC) to mention this.

*** This bug has been marked as a duplicate of bug 54689 ***

[Bug middle-end/78454] valgrind conditional jump or move depends on uninitialised value(s) in sparseset_bit_p

2016-11-21 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78454

Markus Trippelsdorf  changed:

   What|Removed |Added

 CC||trippels at gcc dot gnu.org

--- Comment #1 from Markus Trippelsdorf  ---
Did you configure gcc with --enable-valgrind-annotations?