From: Jan Hubicka <hubicka@kam.mff.cuni.cz>
To: Richard Biener <richard.guenther@gmail.com>
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:25:34 +0100 [thread overview]
Message-ID: <20211111132534.GD17431@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAFiYyc09_hXAhx78ZKvLX3zmLEBJarK7ovw34_-pa5YB+_HHSg@mail.gmail.com>
> > 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.
I think it is also pointer that was allocated and is going to be
freed...
>
> > 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.
Yep, i do not think it understands this. I will look into it - I guess
it is common enough to care about.
Honza
next prev parent reply other threads:[~2021-11-11 13:25 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
2021-11-11 13:25 ` Jan Hubicka [this message]
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=20211111132534.GD17431@kam.mff.cuni.cz \
--to=hubicka@kam.mff.cuni.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).