-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/22/11 02:56, Richard Guenther wrote:
> On Thu, Apr 21, 2011 at 5:47 PM, Jeff Law wrote:
>
> For some dumb reason I thought handling threading through a SWITCH_EXPR
> was hard in VRP; that's definitely not the case, it's no more difficult
> than
On Thu, Apr 21, 2011 at 5:47 PM, Jeff Law wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> For some dumb reason I thought handling threading through a SWITCH_EXPR
> was hard in VRP; that's definitely not the case, it's no more difficult
> than handling a COND_EXPR.
>
> This patch all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/21/11 11:26, Steven Bosscher wrote:
>> Bootstrapped and regression tested on x86_64-unknown-linux-gnu. OK for
>> trunk?
>
> Would this also fix PR18046?
Also note that the assertion machinery doesn't really have the concept
of anti-ranges, much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/21/11 11:26, Steven Bosscher wrote:
>> Bootstrapped and regression tested on x86_64-unknown-linux-gnu. OK for
>> trunk?
>
> Would this also fix PR18046?
Not right now.
If we look at VRP2 (and this only affects VRP's jump threading) we have:
S
> Bootstrapped and regression tested on x86_64-unknown-linux-gnu. OK for
> trunk?
Would this also fix PR18046?
Ciao!
Steven
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For some dumb reason I thought handling threading through a SWITCH_EXPR
was hard in VRP; that's definitely not the case, it's no more difficult
than handling a COND_EXPR.
This patch allows tree-vrp.c to thread through a SWITCH_EXPR when we
know the s