[Bug tree-optimization/80620] [8 Regression] gcc produces wrong code with -O3

2017-07-18 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80620 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/80620] [8 Regression] gcc produces wrong code with -O3

2017-07-18 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80620 --- Comment #8 from Richard Biener --- Author: rguenth Date: Tue Jul 18 07:35:40 2017 New Revision: 250297 URL: https://gcc.gnu.org/viewcvs?rev=250297=gcc=rev Log: 2017-07-18 Richard Biener PR

[Bug tree-optimization/80620] [8 Regression] gcc produces wrong code with -O3

2017-05-04 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80620 --- Comment #7 from Richard Biener --- Now needs sth before r247596 to reproduce. The whole PRE_EXPR_NARY (expr) = newnary; constant = fully_constant_expression (expr); PRE_EXPR_NARY (expr) = nary;

[Bug tree-optimization/80620] [8 Regression] gcc produces wrong code with -O3

2017-05-04 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80620 --- Comment #6 from Richard Biener --- Ugh. This is really another latent issue with PRE and range-info. When PHI-translating {bit_and_expr,a.12_17,4081116982543369} when valueizing a.12_17 we end up with a leader for a.12_17 as

[Bug tree-optimization/80620] [8 Regression] gcc produces wrong code with -O3

2017-05-04 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80620 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED Version|7.0.1