public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
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 Gimple Variables named D.[0-9]*
Date: Mon, 24 Aug 2020 11:24:06 +0200	[thread overview]
Message-ID: <CAFiYyc3VA3=c7GU5Kdg4mzjJTfPBkAySCpB9eJNbVNyhT6fsAA@mail.gmail.com> (raw)
In-Reply-To: <2d3160cb-52b2-9397-d8eb-9da5877f1b30@theobroma-systems.com>

On Thu, Aug 20, 2020 at 11:51 AM Erick Ochoa
<erick.ochoa@theobroma-systems.com> wrote:
>
> Hello,
>
> I am looking at the dump for the build_alias pass. I see a lot of
> variables with the naming convention D.[0-9]* in the points-to sets
> being printed.
>
> When I compile with
>
> -fdump-tree-all-all
>
> I can see that the suffix D.[0-9]* is appended to some gimple variables.
> I initially imagined that variables in the points-to variable set could
> map to a variable declaration in gimple, but this does not seem to be
> the case. I have confirmed this by searching for some known variable
> name in the points-to set and finding no matches in the gimple code, the
> other way around seems to also be true.
>
> Are these variables just constraint variables used to solve the
> points-to analysis? In other words, the variables in points-to sets
> printed out in build_alias do not have a simple map to variables in
> gimple. The only relation is that the intersection between to points-to
> set for variable A with the points-to set of variable B will yield an
> is_alias(A, B) relationship. Is the above true?

The points-to sets in SSA_NAME_POINTER_INFO record DECL_UIDs
which are those printed as D.[0-9]* which is appended to all variables
if you dump with -uid.  The points-to set "names" in the points-to dumps
are internal names created for the constraint vairables - most of the time
based on the program variable names but only loosely coupled.

The translation between constraint variables and program variables is
done in set_uids_in_ptset.

Richard.

>
> Thanks!
>
>

      reply	other threads:[~2020-08-24  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  9:50 Erick Ochoa
2020-08-24  9:24 ` Richard Biener [this message]

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='CAFiYyc3VA3=c7GU5Kdg4mzjJTfPBkAySCpB9eJNbVNyhT6fsAA@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).