https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126110
Drea Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|16.2 |17.0
--- Comment #13 from Drea Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Macleod from comment #12)
> (In reply to Drea Pinski from comment #10)
> > (In reply to Andrew Macleod from comment #9)
> > > Created attachment 65041 [details]
> > > potential patch
> >
> > Thanks for fixing this. I would never guess this.
>
> It was pretty complex :-)
>
> Do we want to fix this in GCC 16 too? There is a minor impact in performance
> on GCC 17 (.4% in VRP) , but it might be more in GCC 16 where we only had
> the single timestamp.
>
> And thus patch will be slightly different. If you want I can check and
> see...
I don't think it is needed. It was more because of a change I was helping with
exposed this. I doubt this will show up anywhere expect with the change and it
is a minor regression to worry about for GCC 16 since dom will catch still.
