https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114403

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Nothing obviously suspicious here ... I wonder if you can attach
177t.ch_vect, 178t.ifcvt and 179t.vect for the case with the single vectorized
bad loop?

Maybe we're running into a latent issue downstream?  What happens if you
disable most followup passes?

Reply via email to