Large amount of valgrind complaints

Running valgrind on the latest ROOT version causes a lot of complaints about "Conditional jump or move depends on uninitialised value(s)" errors. As simple example to reproduce is to run

valgrind --num-callers=30 --log-file=valgrind.txt --gen-suppressions=all \

  --error-limit=no --suppressions=$ROOTSYS/etc/valgrind-root.supp \

  --track-origins=yes -v \ 

 root.exe -l -q -e 'std::cout << "hello world\n";'

This yields 183 errors from 46 contexts. See the attached valgrind.txt for the full output.

My suspicion is that the TObject constructor now is inlined and thus the suppression in place stops working and any use of fBits of a stack allocated object will trigger this warning.