od point, adjusted. Not sure how likely it is we run into PHIs.
>
> > Talking about this, shouldn't pointers be auto_vec for some
> > reasonable N and pointers.quick_push (ptr) instead of safe_push?
>
> Done as well, but we can only use quick_push for the initial one.
&
d later?
Good point, adjusted. Not sure how likely it is we run into PHIs.
> Talking about this, shouldn't pointers be auto_vec for some
> reasonable N and pointers.quick_push (ptr) instead of safe_push?
Done as well, but we can only use quick_push for the initial one.
Re-testing as foll
On Tue, Apr 18, 2023 at 12:33:25PM +0200, Richard Biener wrote:
> Access diagnostics visits the SSA def-use chains to diagnose things like
> dangling pointer uses. When that runs into PHIs it tries to prove
> all incoming pointers of which one is the currently visited use are
> related to decide w
Access diagnostics visits the SSA def-use chains to diagnose things like
dangling pointer uses. When that runs into PHIs it tries to prove
all incoming pointers of which one is the currently visited use are
related to decide whether to keep looking for the PHI def uses.
That turns out to be overly
