public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Erick Ochoa <eochoa@gcc.gnu.org>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Question about points-to analysis, global variables, IPA, and field sensitivity
Date: Tue, 30 Mar 2021 13:44:38 +0200	[thread overview]
Message-ID: <CAFiYyc0QwshpV6LdHGVMFae5=eG0q6dMXGf+RhctW31Z=YS4NA@mail.gmail.com> (raw)
In-Reply-To: <CAJ_nqzj+sewUThEHzzbKU8Suj80YrGBoQ_Vmt8rhL5xfWarNjQ@mail.gmail.com>

On Tue, Mar 30, 2021 at 1:39 PM Erick Ochoa <eochoa@gcc.gnu.org> wrote:
>
> > If the global is module local we should initialize it with NULL, yes.  If it is
> > not module local it should be initialized with NONLOCAL (that's both what
> > should currently happen correctly - it's needed for non-field-sensitive init
> > as well).
> >
>
> Awesome, thanks Richard! One more question: in the context of LTO,
> "module local" means the current partition?

Yes.

> I understand that IPA-PTA is a late SIMPLE_IPA_PASS but my
> understanding of the consequences of this is a little fuzzy. I think
> that IPA-PTA also runs in multiple partitions (unless a flag like
> -flto-partition=none is used), but there might be some issue with
> reduced precision. Perhaps this reduced precision comes from NONLOCAL
> constraints with symbols that cross partitions? (This is just
> speculation on my part, as I mention, my understanding is a little bit
> fuzzy.)

Yes.  Also (obviously) from function definitions not visible and thus
functions treated as external calls when they need not (because of LTO)

Richard.

      reply	other threads:[~2021-03-30 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  8:50 Erick Ochoa
2021-03-30 11:20 ` Richard Biener
2021-03-30 11:39   ` Erick Ochoa
2021-03-30 11:44     ` 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='CAFiYyc0QwshpV6LdHGVMFae5=eG0q6dMXGf+RhctW31Z=YS4NA@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=eochoa@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    /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).