RE: Is VRP is too conservative to identify boolean value 0 and 1?

2011-11-20 Thread Jiangning Liu
> -Original Message- > From: Richard Guenther [mailto:richard.guent...@gmail.com] > Sent: Friday, September 02, 2011 5:07 PM > To: Jiangning Liu > Cc: gcc@gcc.gnu.org > Subject: Re: Is VRP is too conservative to identify boolean value 0 and > 1? > > On

RE: Is VRP is too conservative to identify boolean value 0 and 1?

2011-09-02 Thread Jiangning Liu
1 2:27 PM > To: Jiangning Liu > Cc: gcc@gcc.gnu.org > Subject: Re: Is VRP is too conservative to identify boolean value 0 and > 1? > > On Thu, Sep 1, 2011 at 10:58 PM, Jiangning Liu > wrote: > > D.1249_3: [0, 1] > > D.1250_5: [0, 1] > > D.1251_6: [0, 1] >

Re: Is VRP is too conservative to identify boolean value 0 and 1?

2011-09-02 Thread Richard Guenther
On Fri, Sep 2, 2011 at 7:58 AM, Jiangning Liu wrote: > Hi, > > For the following small case, > > int f(int i, int j) > { >        if (i==1 && j==2) >                return i; >        else >                return j; > } > > with -O2 option, GCC has vrp2 dump like below, > > ==

Re: Is VRP is too conservative to identify boolean value 0 and 1?

2011-09-01 Thread Andrew Pinski
On Thu, Sep 1, 2011 at 10:58 PM, Jiangning Liu wrote: > D.1249_3: [0, 1] > D.1250_5: [0, 1] > D.1251_6: [0, 1] Those are equivalent to [0, MAX] as _Bool only has two different values, 0 and 1 (MAX). Can you explain more about the optimization which you are working on that needs the ranges as (in