From: Richard Biener <richard.guenther@gmail.com>
To: Erick Ochoa <erick.ochoa@theobroma-systems.com>
Cc: "GCC Development" <gcc@gcc.gnu.org>,
"Philipp Tomsich" <philipp.tomsich@theobroma-systems.com>,
"Christoph Müllner" <christoph.muellner@theobroma-systems.com>
Subject: Re: Question about IPA-PTA and build_alias
Date: Mon, 24 Aug 2020 09:40:19 +0200 [thread overview]
Message-ID: <CAFiYyc3R7DCVMmbr-XPU9tHtwdJsniREmUqCGqxrffRtHAwAJg@mail.gmail.com> (raw)
In-Reply-To: <a6460fa9-204d-a471-7ab3-6fb056e2ac37@theobroma-systems.com>
On Mon, Aug 17, 2020 at 3:22 PM Erick Ochoa
<erick.ochoa@theobroma-systems.com> wrote:
>
> Hello,
>
> I'm looking to understand better the points-to analysis (IPA-PTA) and
> the alias analysis (build_alias).
>
> How is the information produced by IPA-PTA consumed?
>
> Are alias sets in build_alias computed by the intersections of the
> points_to_set(s) (computed by IPA-PTA)?
>
> My intuition tells me that it could be relatively simple to move
> build_alias to be an SIMPLE_IPA_PASS performed just after IPA-PTA, but I
> do not have enough experience in GCC to tell if this is correct. What
> could be some difficulties which I am not seeing? (Either move, or
> create a new IPA-ALIAS SIMPLE_IPA_PASS.) This pass would have the same
> sensitivity as IPA-PTA { flow-insensitive, context-insensitive,
> field-sensitive } because the alias sets could be computed by the
> intersection of points-to-sets.
Both IPA-PTA and build_alias do the same, they build PTA constraint
sets, solve them and attach points-to info to SSA names. Just IPA-PTA
does this for the whole TU while build_alias does it for a function at a time.
So I guess I do not understand your question.
Richard.
>
> Thanks!
next prev parent reply other threads:[~2020-08-24 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 13:20 Erick Ochoa
2020-08-24 7:40 ` Richard Biener [this message]
2020-08-24 8:00 ` Erick Ochoa
2020-08-25 15:16 ` 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=CAFiYyc3R7DCVMmbr-XPU9tHtwdJsniREmUqCGqxrffRtHAwAJg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=christoph.muellner@theobroma-systems.com \
--cc=erick.ochoa@theobroma-systems.com \
--cc=gcc@gcc.gnu.org \
--cc=philipp.tomsich@theobroma-systems.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).