diff options
author | Richard Sandiford <richard.sandiford@linaro.org> | 2017-09-21 10:53:40 +0000 |
---|---|---|
committer | Richard Sandiford <rsandifo@gcc.gnu.org> | 2017-09-21 10:53:40 +0000 |
commit | 53cb6378dfbe32638607251ac2469919eee86df1 (patch) | |
tree | 59b4e3115a78832a2f6d4c77bc03dc1469d6a21d /gcc/errors.c | |
parent | 2e1dd13741b328e317e511e7930738473e4463ac (diff) | |
download | gcc-53cb6378dfbe32638607251ac2469919eee86df1.zip gcc-53cb6378dfbe32638607251ac2469919eee86df1.tar.gz gcc-53cb6378dfbe32638607251ac2469919eee86df1.tar.bz2 |
Add missing int_cst_rangeN checks to tree-vrp.c
The BIT_AND_EXPR handling in extract_range_from_binary_expr_1
was using value_range_constant_singleton without first checking
whether the range was a constant. The earlier handling was correctly
guarded:
/* If either input range contains only non-negative values
we can truncate the result range maximum to the respective
maximum of the input range. */
if (int_cst_range0 && tree_int_cst_sgn (vr0.min) >= 0)
wmax = wi::min (wmax, vr0.max, TYPE_SIGN (expr_type));
if (int_cst_range1 && tree_int_cst_sgn (vr1.min) >= 0)
wmax = wi::min (wmax, vr1.max, TYPE_SIGN (expr_type));
so this patch uses the same guards again.
Existing tests showed the need for this once polynomial constants
are added.
2017-09-21 Richard Sandiford <richard.sandiford@linaro.org>
Alan Hayward <alan.hayward@arm.com>
David Sherwood <david.sherwood@arm.com>
gcc/
* tree-vrp.c (extract_range_from_binary_expr_1): Check
int_cst_rangeN before calling value_range_constant_singleton (&vrN).
Co-Authored-By: Alan Hayward <alan.hayward@arm.com>
Co-Authored-By: David Sherwood <david.sherwood@arm.com>
From-SVN: r253054
Diffstat (limited to 'gcc/errors.c')
0 files changed, 0 insertions, 0 deletions