https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107639
--- Comment #3 from Andrew Macleod <amacleod at redhat dot com> ---
(In reply to Richard Biener from comment #2)
> Confirmed. Something for ranger/VRP "symbolic" handling.
I'm not so sure. what is related? there are 2 loop values being bumped by
different amounts. the loop is controlled by the it pointer, which is bumped
by 4. The only connection between len5 and idx_14 is thru the calculation of
end_7, which boils down to is begin+len_5 * 4. theres no way ranger is making
that connection now.
The loop boils down to:
<bb 2> [local count: 118111600]:
_1 = (long unsigned int) len_5(D);
_2 = _1 * 4;
end_7 = begin_6(D) + _2;
if (begin_6(D) != end_7)
goto <bb 5>; [89.00%]
<bb 3> [local count: 850510901]:
if (len_5(D) >= idx_14) // how to know this is always true
goto <bb 5>; [100.00%]
else
goto <bb 4>; [0.00%]
<bb 5> [local count: 955630225]:
# idx_17 = PHI <idx_14(3), 0(5)>
# it_18 = PHI <it_13(3), begin_6(D)(5)>
it_13 = it_18 + 4;
idx_14 = idx_17 + 1;
if (end_7 != it_13)
goto <bb 3>; [89.00%]
else
goto <bb 6>; [11.00%]
This seems more like a loop thing. both values are being bumped by the loop,
and the end condition is based on a calculation using len_5.. it seems like it
should now the bounds of both ir and idx? or maybe it does and cant
communicate it any more?
