https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107197
--- Comment #1 from David Binderman <dcb314 at hotmail dot com> --- I can tell you that last weekend's valgrind build with -O2 went fine. That was from git hash ca01d2526917ec6e. This weekend's valgrind build, with -O3 enabled, is from git hash 6ffbf87ca66f4ed9cd79cff675fabe2109e46e85. So either someone has broken something this week in -O2, or -O3 has been broken for longer. I will take the -O3 off this weekend's build, drop back to -O2 and see what happens.
