https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110643
--- Comment #18 from psykose <alice at ayaya dot dev> --- > Could you please run a regression to identify which commit along GCC-13 > branch introduce the change at least to get the ball rolling ? note that it might not actually be a regression; it's possible the cvise minimisation (above) results in "easy to spot UB in testcase" because the original (non-minimised) program was actually broken because of UB somewhere (with newer gcc then breaking it via new optimisations), just with it being harder to find. knowing which commit causes the final bad output may or may not help find that, if it's the case. the investigation hasn't concluded quite yet.
