[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-18 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 Jakub Jelinek changed: What|Removed |Added CC||su at cs dot ucdavis.edu --- Comment #5

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-18 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 --- Comment #6 from Jakub Jelinek --- *** Bug 69342 has been marked as a duplicate of this bug. ***

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-18 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 Jakub Jelinek changed: What|Removed |Added CC||chengniansun at gmail dot com ---

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-18 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 --- Comment #7 from Markus Trippelsdorf --- *** Bug 69322 has been marked as a duplicate of this bug. ***

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-18 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 --- Comment #8 from Jeffrey A. Law --- Jakub. I'll certainly backtest against the referenced BZs While the fix is trivial, I'm seriously considering just turning the exploitation of ranges off for gcc-6. It didn't help as much as I had wanted

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-18 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 --- Comment #9 from Jeffrey A. Law --- I've backtested against all 4 duplicates and my change fixes all of them.

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-18 Thread law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 --- Comment #10 from Jeffrey A. Law --- Author: law Date: Tue Jan 19 06:43:54 2016 New Revision: 232548 URL: https://gcc.gnu.org/viewcvs?rev=232548=gcc=rev Log: 2016-01-18 Jeff Law PR tree-optimization/69320

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-18 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 --- Comment #11 from Jeffrey A. Law --- Fixed by commit on the trunk.

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-18 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-17 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #3

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-16 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |6.0 Summary|wrong code

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-16 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 Jeffrey A. Law changed: What|Removed |Added Priority|P3 |P1 CC|

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-16 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug tree-optimization/69320] [6 Regression] wrong code generation at -O2 and higher

2016-01-16 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69320 --- Comment #2 from Jeffrey A. Law --- Ha! Got it. On the path noted in the earlier comment we have the following: : pred_x ={v} {CLOBBER}; pred_y ={v} {CLOBBER}; _423 = s_46(D)->rd_total; _424 = score[best_374]; _425 = (long int) _424; _426