https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119966
--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Dimitar Dimitrov from comment #10) > This issue was fixed with r16-809-gf725d6765373f7. That commit was not even supposed to fix this either. Even though that did fix the issue that exposed by the same patch as this one. I suspect the reason how r16-809 fixed it is the same way r16-809 fixed the missed optimization; that is causing combine to optimize back the same way it was doing before r16-160 and not exposing the issue that late combine with r16-160 exposes. So maybe it became latent again.
