[Bug tree-optimization/17100] Missed opportunity for value range optimization

2005-09-10 Thread pinskia at gcc dot gnu dot org
-- Bug 17100 depends on bug 18373, which changed state. Bug 18373 Summary: [meta-bug] VRP Value Range Propagation http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18373 What|Old Value |New Value ---

[Bug tree-optimization/17100] Missed opportunity for value range optimization

2005-06-02 Thread dnovillo at gcc dot gnu dot org
--- Additional Comments From dnovillo at gcc dot gnu dot org 2005-06-02 18:50 --- Fixed. Likely with http://gcc.gnu.org/ml/gcc-patches/2005-06/msg00127.html, but it may have been fixed earlier. The natural range for i_6 is computed as [0, 9] so this isn't something that was folded usi

[Bug tree-optimization/17100] Missed opportunity for value range optimization

2005-04-24 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-24 11:48 --- i_8: VARYING # i_8 = PHI <0(0), i_10(4)>; :; if (i_8 == -5) goto ; else goto ; i_10 = i_8 + 1; if (i_10 <= 9) goto ; else goto ; i_10: [1, 2147483647] Hmm, isn't i_10 signed still so why betwee

[Bug tree-optimization/17100] Missed opportunity for value range optimization

2004-12-19 Thread sebastian dot pop at cri dot ensmp dot fr
--- Additional Comments From sebastian dot pop at cri dot ensmp dot fr 2004-12-19 23:43 --- Patch in autovect-branch: http://gcc.gnu.org/ml/gcc-patches/2004-12/msg01444.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17100

[Bug tree-optimization/17100] Missed opportunity for value range optimization

2004-10-12 Thread nathan at gcc dot gnu dot org
--- Additional Comments From nathan at gcc dot gnu dot org 2004-10-12 10:34 --- I think this is an artifact of the design of the current value range propagation. That's not really range propagation by comparison result CSEing. The loop exit is i < 10, and the next comparison is i == 15