[Bug tree-optimization/100958] two_value_replacement should move to match.pd

2023-04-28 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100958 Andrew Pinski changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug tree-optimization/100958] two_value_replacement should move to match.pd

2023-04-28 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100958 --- Comment #3 from CVS Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:1dd154f6407658d46faa4d21bfec04fc2551506a commit r14-338-g1dd154f6407658d46faa4d21bfec04fc2551506a Author: Andrew Pinski Date: Tue

[Bug tree-optimization/100958] two_value_replacement should move to match.pd

2023-04-25 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100958 --- Comment #2 from Andrew Pinski --- Created attachment 54923 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54923&action=edit Patch which is under testing

[Bug tree-optimization/100958] two_value_replacement should move to match.pd

2023-04-09 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100958 --- Comment #1 from Andrew Pinski --- Here is the start of the conversion to match.pd, there must be an easier way to see the range too: #if GIMPLE /* Optimize x in range [cst1, cst2] where cst2 = cst1 + 1 (x op CSTN) ? CST3 : CST4 # wh

[Bug tree-optimization/100958] two_value_replacement should move to match.pd

2021-06-07 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100958 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2021-06-08 Ever confirmed|0