[Bug tree-optimization/42108] [4.6/4.7/4.8 Regression] 50% performance regression

2013-01-17 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42108 --- Comment #57 from Richard Biener 2013-01-17 14:42:11 UTC --- A proper fix these days (with tuples) is to add new tree codes that carry the knowledge that countm1.6_40 = _38 / _39; may not trap. The frontend already knows this (s

[Bug tree-optimization/42108] [4.6/4.7/4.8 Regression] 50% performance regression

2013-01-17 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42108 --- Comment #56 from Richard Biener 2013-01-17 14:30:10 UTC --- 4.3 vs. trunk I get 9.5s vs. 12.3s for -O3. With 4.7 and 4.6 I get the same result (on Intel CPUs). Thus basically re-confirmed after the recent patches.

[Bug tree-optimization/42108] [4.6/4.7/4.8 Regression] 50% performance regression

2013-01-17 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42108 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- C

[Bug tree-optimization/42108] [4.6/4.7/4.8 Regression] 50% performance regression

2013-01-16 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42108 --- Comment #54 from Richard Biener 2013-01-16 12:36:52 UTC --- Re-confirmed on trunk. The initial GFortran IL is still ... awkward. Apart from the issue of using a canonicalized IV at all we have D.1910 = i