Re: [COMMITTED 03/16] Make some Value_Range's explicitly integer.

Ughhh, you're right. Thanks for spotting this. I'm testing the attached patch and will commit if it passes tests. Aldy On Tue, Apr 30, 2024 at 9:46 AM Richard Biener wrote: > > On Sun, Apr 28, 2024 at 9:07 PM Aldy Hernandez wrote: > > > > Fix some Value_Range's that we know ahead of time will

Re: [COMMITTED 03/16] Make some Value_Range's explicitly integer.

On Sun, Apr 28, 2024 at 9:07 PM Aldy Hernandez wrote: > > Fix some Value_Range's that we know ahead of time will be only > integers. This avoids using the polymorphic Value_Range unnecessarily But isn't Value_Range a variable-size irange but int_range<2> doesn't support more than two sub-ranges?

[COMMITTED 03/16] Make some Value_Range's explicitly integer.

Fix some Value_Range's that we know ahead of time will be only integers. This avoids using the polymorphic Value_Range unnecessarily gcc/ChangeLog: * gimple-ssa-warn-access.cc (check_nul_terminated_array): Make Value_Range an int_range. (memmodel_to_uhwi): Same * tree-ss