https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96395
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Sandra: what is the status of your loop unification changes? FWIW, I'm not able to reproduce this issue with trunk. Note that g:fd111c419d146ee47c7df9a36a535e8d843d4802 fixed a state-explosion bug in how switch statements are handled, so perhaps that fixed it. That said, there's merit in generalizing the C tests so they run for both C and C++, so maybe this bug should track that.
