[Bug c/105013] Valgrind reports accessing uninitialized memory when -O2 option is used

[marxin at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105013

--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
I can't reproduce it with valgrind 3.17 where I tried various GCC versions.
Can you please test using valgrind with --expensive-definedness-checks=yes?

Please attach assembly file that causes that (-S) option.