This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Is VRP is too conservative to identify boolean value 0 and 1?
- From: "Jiangning Liu" <jiangning dot liu at arm dot com>
- To: "'Andrew Pinski'" <pinskia at gmail dot com>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Fri, 2 Sep 2011 17:54:42 +0800
- Subject: RE: Is VRP is too conservative to identify boolean value 0 and 1?
- References: <4e607315.5117e70a.25cb.ffffb31eSMTPIN_ADDED@mx.google.com> <CA+=Sn1nPPmaD47r3SPY4mv0tvWgO741i8vTTzbtfKAXbbr-26Q@mail.gmail.com>
Andrew,
I realize I needn't back-end solution for my case at all, and in middle end I can directly use the _Bool type info! Appreciate your reply!
Thanks,
-Jiangning
> -----Original Message-----
> From: Andrew Pinski [mailto:pinskia@gmail.com]
> Sent: Friday, September 02, 2011 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 <jiangning.liu@arm.com>
> 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 (int)[0,1] rather
> than (_Bool)[0,MAX] ?
>
> Thanks,
> Andrew Pinski