| commit | 0b2735e0797fee9b4ec5cd74f22afe0483f888dd | |
| author | Aldy Hernandez <aldyh@redhat.com> | |
| Tue, 30 Apr 2024 08:36:58 +0000 (30 10:36 +0200) | ||
| committer | Aldy Hernandez <aldyh@redhat.com> | |
| Tue, 30 Apr 2024 12:46:01 +0000 (30 14:46 +0200) | ||
| tree | a83141cc527f59c593a4c1d1568f987520ab3c14 | treesnapshot (tar.gz zip) |
| parent | aff63ac11099d100b6891f3bcc3dc6cbc4fad654 | commitdiff |
Change int_range<2> to infinite precision.
In my previous change I mistakenly changed Value_Range to
int_range<2>. The former has "infinite" precision for integer ranges,
whereas int_range<2> has two sub-ranges. This should have been
int_range_max.
gcc/ChangeLog:
* gimple-ssa-warn-access.cc (check_nul_terminated_array): Change
int_range<2> to int_range_max.
(memmodel_to_uhwi): Same.
* tree-ssa-loop-niter.cc (refine_value_range_using_guard): Same.
(determine_value_range): Same.
(infer_loop_bounds_from_signedness): Same.
(scev_var_range_cant_overflow): Same.
In my previous change I mistakenly changed Value_Range to
int_range<2>. The former has "infinite" precision for integer ranges,
whereas int_range<2> has two sub-ranges. This should have been
int_range_max.
gcc/ChangeLog:
* gimple-ssa-warn-access.cc (check_nul_terminated_array): Change
int_range<2> to int_range_max.
(memmodel_to_uhwi): Same.
* tree-ssa-loop-niter.cc (refine_value_range_using_guard): Same.
(determine_value_range): Same.
(infer_loop_bounds_from_signedness): Same.
(scev_var_range_cant_overflow): Same.
| gcc/gimple-ssa-warn-access.cc | diffblobblamehistory | |
| gcc/tree-ssa-loop-niter.cc | diffblobblamehistory |