On Mon, 9 Nov 2020, Jan Hubicka wrote:
> > > But it also means that some of our FNSPECs are wrong now. I wonder if we
> > > can
> > > split this porperty to two different flags like EAF_NOEASCAPE and
> > > EAF_INDIRECT_NOESCAPE?
> >
> > Note that EAF_NOESCAPE allows "escaping" to the return
> > But it also means that some of our FNSPECs are wrong now. I wonder if we
> > can
> > split this porperty to two different flags like EAF_NOEASCAPE and
> > EAF_INDIRECT_NOESCAPE?
>
> Note that EAF_NOESCAPE allows "escaping" to the return value (see
> handle_rhs_call). I guess for simplicity
On Sun, 8 Nov 2020, Jan Hubicka wrote:
> Hi,
> I implemented simple propagation of EAF arguments for ipa-modref (that is not
> hard to do). My main aim was to detect cases where THIS parameter does not
> escape but is used to read/write pointed to memory. This is meant to
> avoid poor code
Hi,
I implemented simple propagation of EAF arguments for ipa-modref (that is not
hard to do). My main aim was to detect cases where THIS parameter does not
escape but is used to read/write pointed to memory. This is meant to
avoid poor code produced when we i.e. offline destructors on cold
