https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91491
--- Comment #5 from Simon McVittie <smcv at debian dot org> --- > I suppose you did things like running under valgrind or compiling with -fsanitize=address. I wasn't able to reproduce the bug earlier on, in a build with -fsanitize=address, but this was probably because I was focusing on GLib and not Clutter. valgrind reveals that the (already compiled) Clutter test (not the part we were recompiling) wasn't fully initializing a struct on the stack. > The most obvious thing I expect from -fno-tree-pre > is stack layout changes which then smells like some bogus stack smashing > going on. Enabling or disabling the optimization resulted in the uninitialized part of the struct (apparently reliably) containing a zero or nonzero value. If it's nonzero, the rest of the test is effectively skipped, so it has no opportunity to hang. It's entirely possible that the test in question has never worked correctly - when I initialize the struct to all-zeroes (which appears to have been the intention), it reliably hangs. So I think this can be closed as not your bug. Sorry for the noise.
