From: Richard Biener <richard.guenther@gmail.com>
To: Jan Hubicka <hubicka@kam.mff.cuni.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Use modref summary to DSE calls to non-pure functions
Date: Thu, 11 Nov 2021 14:20:32 +0100 [thread overview]
Message-ID: <CAFiYyc09_hXAhx78ZKvLX3zmLEBJarK7ovw34_-pa5YB+_HHSg@mail.gmail.com> (raw)
In-Reply-To: <20211111124243.GA17431@kam.mff.cuni.cz>
On Thu, Nov 11, 2021 at 1:42 PM Jan Hubicka <hubicka@kam.mff.cuni.cz> wrote:
>
> Hi,
> >
> > No, I think if it turns out useful then we want a way to have such ref
> > represented by an ao_ref. Note that when we come from a
> > ref tree we know handled-components only will increase offset,
> > only the base MEM_REF can contain a pointer subtraction (but
> > the result of that is the base then).
>
> Yep, that is why I introduced the parm_offset at first place - it can be
> negative or unknown...
> >
> > In what cases does parm_offset_known end up false? Is that
> > when seeing a POINTER_PLUS_EXPR with unknown offset?
>
> Yep, a typical example is a loop with pointer walking an array .
>
> > So yes, that's a case we cannot capture right now - the only
> > thing that remains is a pointer with a known points-to-set - a
> > similar problem as with the pure call PRE. You could in theory
> > allocate a scratch SSA name and attach points-to-info
> > to it. And when the call argument is &decl based then you could set
> > offset to zero.
>
> Hmm, I could try to do this, but possibly incrementally?
You mean handle a &decl argument specially for unknown param offset?
Yeah, I guess so.
> Basically I want to have
>
> foo (&decl)
> decl = {}
>
> To be matched since even if I do not know the offset I know it is dead
> after end of lifetime of the decl. I am not quite sure PTA will give me
> that?
for this case PTA should tell you the alias is to 'decl' only but then I'm
not sure if stmt_kills_ref_p is up to the task to determine that 'decl = {}',
from a quick look it doesn't. So indeed the only interesting case will
be a &decl based parameter which we can special-case.
> > > It was my initial plan. However I was not sure how much I would get from
> > > that.
> > >
> > > The function starts with:
> > >
> > > /* Don't return early on *this_2(D) ={v} {CLOBBER}. */
> > > if (gimple_has_volatile_ops (stmt)
> > > && (!gimple_clobber_p (stmt)
> > > || TREE_CODE (gimple_assign_lhs (stmt)) != MEM_REF))
> > > return;
> > >
> > > ao_ref ref;
> > > if (!initialize_ao_ref_for_dse (stmt, &ref))
> > > return;
> > >
> > > The check about clobber does not apply to calls and then it gives up on
> > > functions not returning aggregates (that is a common case).
> > >
> > > For functions returing aggregates it tries to prove that retval is dead
> > > and replace it.
> > >
> > > I guess I can simply call my analysis from the second return above and
> > > from the code removing dead LHS call instead of doing it from the main
> > > walker and drop the LHS handling?
> >
> > Yeah, something like that.
> OK, I will prepare updated patch, thanks!
>
> Honza
> >
> > Richard.
> >
> > > Thank you,
> > > Honza
> > > >
> > > > Thanks,
> > > > Richard.
> > > >
> > > > > + }
> > > > > else if (def_operand_p
> > > > > def_p = single_ssa_def_operand (stmt, SSA_OP_DEF))
> > > > > {
next prev parent reply other threads:[~2021-11-11 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 12:43 Jan Hubicka
2021-11-11 11:14 ` Richard Biener
2021-11-11 12:07 ` Jan Hubicka
2021-11-11 12:32 ` Richard Biener
2021-11-11 12:42 ` Jan Hubicka
2021-11-11 13:20 ` Richard Biener [this message]
2021-11-11 13:25 ` Jan Hubicka
2021-11-12 11:39 ` Jan Hubicka
2021-11-12 12:53 ` Richard Biener
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFiYyc09_hXAhx78ZKvLX3zmLEBJarK7ovw34_-pa5YB+_HHSg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@kam.mff.cuni.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).