https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120218
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The peformance issue in May was fixed between r16-566-gb5f48e7872db30 and r16-427-g86627faec10da5 (most likely one of the cost fixes for the x86 backend). But there is worse one in July that is still around, introduced between r16-2618-g241380c6d632eb and r16-2491-g257b640d256d3f.
