On 9/17/18 4:12 AM, Aldy Hernandez wrote:
> It seems most of the remaining anti range code in
> extract_range_from_unary_expr for CONVERT_EXPR_P is actually dealing
> with non-nullness in practice.
>
> Anti-range handling is mostly handled by canonicalizing anti-ranges into
> its two set constitue
PING * 2
Forwarded Message
Subject: PING: Re: VRP: special case all pointer conversion code
Date: Wed, 26 Sep 2018 13:12:19 -0400
From: Aldy Hernandez
To: gcc-patches
CC: Jeff Law
PING
On 9/17/18 6:12 AM, Aldy Hernandez wrote:
It seems most of the remaining anti range
PING
On 9/17/18 6:12 AM, Aldy Hernandez wrote:
It seems most of the remaining anti range code in
extract_range_from_unary_expr for CONVERT_EXPR_P is actually dealing
with non-nullness in practice.
Anti-range handling is mostly handled by canonicalizing anti-ranges into
its two set constituen
It seems most of the remaining anti range code in
extract_range_from_unary_expr for CONVERT_EXPR_P is actually dealing
with non-nullness in practice.
Anti-range handling is mostly handled by canonicalizing anti-ranges into
its two set constituents (~[10,20] => [MIN,9] U [21,MAX]) and dealing
