https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62025
--- Comment #16 from Jeffrey A. Law <law at redhat dot com> --- In reference to c#12. I think the ivopts changes are just setting up the situation that is mis-handled later. I'd gotten as far as seeing the +128 increment moving in the scheduler, but hadn't looked to see if it was valid. Anyway, so yes I think the ivopts stuff is fine. I should have realized I was chasing something of that nature when the bisection settled on the ivopts code as the trigger.
