> Hi,
>
> On Wed, Oct 14 2020, Jan Hubicka wrote:
> > Hi,
> > here is updated patch with cap on number of iterations.
> > I set the limit to 8 and bootstrapped it with additional assert that the
> > limit is not met, it did not fire.
> >
> > Bootstrapped/regtested x86_64-linux, OK?
> >
> > gcc/Cha
Hi,
On Wed, Oct 14 2020, Jan Hubicka wrote:
> Hi,
> here is updated patch with cap on number of iterations.
> I set the limit to 8 and bootstrapped it with additional assert that the
> limit is not met, it did not fire.
>
> Bootstrapped/regtested x86_64-linux, OK?
>
> gcc/ChangeLog:
>
> 2020-10-14
On Wed, 14 Oct 2020, Jan Hubicka wrote:
> Hi,
> here is updated patch with cap on number of iterations.
> I set the limit to 8 and bootstrapped it with additional assert that the
> limit is not met, it did not fire.
>
> Bootstrapped/regtested x86_64-linux, OK?
OK.
Richard.
> gcc/ChangeLog:
>
Hi,
here is updated patch with cap on number of iterations.
I set the limit to 8 and bootstrapped it with additional assert that the
limit is not met, it did not fire.
Bootstrapped/regtested x86_64-linux, OK?
gcc/ChangeLog:
2020-10-14 Jan Hubicka
* doc/invoke.texi: (ipa-jump-function
> On Tue, 13 Oct 2020, Jan Hubicka wrote:
>
> > > > So I implemented my own pattern matching and I think we should switch
> > > > ipa-prop
> > > > on it incrementally. It is based on similar logic in
> > > > ao_ref_init_from_ptr_and_size.
> > >
> > > So instead of re-inventing the wheel what abo
On Tue, 13 Oct 2020, Jan Hubicka wrote:
> > > So I implemented my own pattern matching and I think we should switch
> > > ipa-prop
> > > on it incrementally. It is based on similar logic in
> > > ao_ref_init_from_ptr_and_size.
> >
> > So instead of re-inventing the wheel what about splitting out
> > So I implemented my own pattern matching and I think we should switch
> > ipa-prop
> > on it incrementally. It is based on similar logic in
> > ao_ref_init_from_ptr_and_size.
>
> So instead of re-inventing the wheel what about splitting out a
> common helper instead?
It was my original idea.
On Tue, 13 Oct 2020, Jan Hubicka wrote:
> Hi,
> this patch makes local modref to track parameters that are passed through with
> and adjustment (via pointer_plus or addr_expr of mem_ref). I intended to
> re-use
> logic in ipa-prop, but it turns out that it is weird:
> if (TREE_CODE (op1) != AD
> Hi,
> this patch makes local modref to track parameters that are passed through with
> and adjustment (via pointer_plus or addr_expr of mem_ref). I intended to
> re-use
> logic in ipa-prop, but it turns out that it is weird:
> if (TREE_CODE (op1) != ADDR_EXPR)
> return;
> op1 = TREE_OPE
