[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 Andrew Pinski pinskia at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 --- Comment #8 from Andrew Pinski pinskia at gcc dot gnu.org 2012-03-09 09:27:35 UTC --- Author: pinskia Date: Fri Mar 9 09:27:29 2012 New Revision: 185131 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=185131 Log: 2012-03-09 Andrew

[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 --- Comment #7 from Andrew Pinski pinskia at gcc dot gnu.org 2012-01-25 21:35:01 UTC --- Here is another testcase (which passes with the patch I posted but does not with a patch which I created internally to create COND_EXPR's). int g(int,int);

[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 Andrew Pinski pinskia at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last

[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 Andrew Pinski pinskia at gcc dot gnu.org changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 --- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org 2012-01-25 00:04:01 UTC --- Note this is like http://gcc.gnu.org/ml/gcc-patches/2012-01/msg01195.html but different as we should do this even if the arguments for the other PHIs are non

[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 --- Comment #3 from Andrew Pinski pinskia at gcc dot gnu.org 2012-01-25 00:24:41 UTC --- Here is a better testcase: int g(int,int); int f(int t, int c) { int d = 0; int e = 0; if (t) { d = 1; e = t; } else d = 0, e =

[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 --- Comment #4 from Andrew Pinski pinskia at gcc dot gnu.org 2012-01-25 00:26:41 UTC --- The first testcase is still valid but is not handled currently without some changes dealing with how PHI-OPT works which I am fixing right now.

[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 --- Comment #5 from Andrew Pinski pinskia at gcc dot gnu.org 2012-01-25 00:45:37 UTC --- Here is another testcase which also fails: int g(int,int); int f(int t, int c) { int d = 0; int e = 0; if (t) { d = c+1; e = t; }

[Bug tree-optimization/51988] value_replacement in PHIOPT should handle even the cases where there are other PHIs even with non equal value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51988 --- Comment #6 from Andrew Pinski pinskia at gcc dot gnu.org 2012-01-25 00:58:45 UTC --- I have a patch which fixes the testcases in comment #3 and comment #5. The testcase in comment #0 will be fixed with the patch in