On Mon, 12 Feb 2018, Jakub Jelinek wrote:
> Hi!
>
> get_range_strlen fails to tell the caller that array_at_struct_end_p has
> been involved in cases like (&ptr->arr[0]), while it handles
> (ptr->arr). Fixed thusly, bootstrapped/regtested on x86_64-linux and
> i686-linux, ok for trunk?
Ok.
Ric
Hi!
get_range_strlen fails to tell the caller that array_at_struct_end_p has
been involved in cases like (&ptr->arr[0]), while it handles
(ptr->arr). Fixed thusly, bootstrapped/regtested on x86_64-linux and
i686-linux, ok for trunk?
2018-02-12 Jakub Jelinek
PR tree-optimization/84339