On Thu, 22 Jan 2026, Maciej W. Rozycki wrote: > > I suspect that it's some function of the language being compiled (C++ vs C), > > the complexity of the input, the optimisation level requested and the phase > > of > > the moon. I do know that GCC 12.2.0 also terminated abruptly under the same > > circumstances and that the reproduction case was quite a bit smaller. I'll > > send you some more details of my build environment off-list. > > Weird, but the issue does trigger here with your reproducer included with > the PR, so it's good enough to work with. Compilation succeeds with GCC > 11 though, so it's indeed a regression and might be related to the switch > from CC0 to MODE_CC internal condition code representation. I might try > to bisect it.
Indeed it is: # first bad commit: [e552abe2ba27ccec0d7c0d050b4617f2f636dd63] PR target/95294: VAX: Convert backend to MODE_CC representation where these patterns have been introduced. I have updated your fix by integrating the testcase you have provided and adjusting the commit heading and description according to our contribution rules at: <https://gcc.gnu.org/contribute.html#patches>. Please give it a read at your convenience for your future submissions. I have committed it now and will wait a little for any fallout from the testcase, since I made it generic, before backporting it to the release branches. Thank you for your contribution. Maciej
