[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 --- Comment #12 from Richard Biener --- In fact I wonder how the code would support any case where the VUSE on the later load isn't the same as the VUSE on the first load.

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 --- Comment #11 from Richard Biener --- (In reply to rguent...@suse.de from comment #10) > On Tue, 10 Dec 2024, pinskia at gcc dot gnu.org wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 > > > > --- Comment #7 from Andrew Pins

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 --- Comment #10 from rguenther at suse dot de --- On Tue, 10 Dec 2024, pinskia at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 > > --- Comment #7 from Andrew Pinski --- > Created attachment 59825 > --> https:

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 --- Comment #9 from Richard Biener --- (In reply to Andrew Pinski from comment #8) > I am suspecting this comes from a benchmark, do you have the name of the > benchmark? Nope, it got reported to me with just exactly this testcase ...

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 --- Comment #8 from Andrew Pinski --- I am suspecting this comes from a benchmark, do you have the name of the benchmark?

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 --- Comment #7 from Andrew Pinski --- Created attachment 59825 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59825&action=edit Fix Note this includes debugging still and no testcases. And has only done some quick testing on the testcases

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 Andrew Pinski changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 Andrew Pinski changed: What|Removed |Added Attachment #59823|0 |1 is obsolete|

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 --- Comment #4 from Andrew Pinski --- (In reply to Andrew Pinski from comment #2) > Confirmed. Hmm, phiprop2 can handle it though; that is > -fdisable-tree-phiprop1 and see that phiprop2 handles it. > > I have not looked into why yet. That is

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 --- Comment #3 from Andrew Pinski --- Looks like exceptions. That is for my reduced testcase adding -fno-exceptions works.

[Bug tree-optimization/117965] phiprop fails in some cases

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117965 --- Comment #1 from Andrew Pinski --- Created attachment 59823 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59823&action=edit reduced testcase Add -DWORKS and phiprop works. That is the call before clamp is causing issues. (maybe vops