http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57192

Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
                 CC|                            |steven at gcc dot gnu.org
         Resolution|---                         |FIXED

--- Comment #17 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> 
---
So, after some bisection, I find that the valgrind warning appears due to:

r190503 | steven | 2012-08-18 15:44:00 +0200 (Sat, 18 Aug 2012) | 4 lines

    * sparseset.c (sparseset_alloc): Use non-clearing allocation.  Tell
    valgrind not to worry about reading from unitialized memory.

so, for whatever reason this doesn't work on my setup. 

Steven, what is needed to have these valgrind hints enabled ? Are these
valgrind hints enabled by default ?

BTW, this also clearly shows that at this point this PR is unrelated to SLSR
and fixed.

Reply via email to