------- Comment #3 from vmakarov at redhat dot com 2010-02-03 18:57 ------- This is a rare case when the algorithm works the same whatever values are in memory. Roughly speaking, if the value is not as expected (for example a garbage) the value is set up to what it needed. If it is one as expected we do nothing and have the same result. Valgrind warns because the data is not initialized.
I'll submit a patch soon for initialization of the values. The compiler will work absolutely the same (may be a bit slower because of the initialization) but there will be no valgrind warnings which will simplify compiler debugging by valgrind. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42941
