From: Richard Biener <richard.guenther@gmail.com>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.
Date: Tue, 1 Jun 2021 09:34:52 +0200 [thread overview]
Message-ID: <CAFiYyc2wUhFMP5Xy9e=USDfLbTjUbROTdkG0ka=8wvh9TcdzDQ@mail.gmail.com> (raw)
In-Reply-To: <9250230f-a9ff-c30f-4fad-9f7fdeaf52ec@redhat.com>
On Tue, Jun 1, 2021 at 3:38 AM Andrew MacLeod via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> An ongoing issue is the the order we evaluate things in can affect
> decisions along the way. As ranger isn't a fully iterative pass, we can
> sometimes come up with different results if back edges are processed in
> different orders.
>
> One of the ways this can happen is when the cache is propagating
> on-entry values for an SSA_NAME. It calculates outgoing edge values and
> the gori-compute engine can flag ssa-names that were involved in a range
> calculation that have not yet been initialized. When the propagation
> for the original name is done, it goes back and examines the "poor
> values" and tries to quickly calculate a better range, and if it comes
> up with one, immediately tries to go back and update the location/range
> gori_compute flagged. This produces better ranges earlier.
>
> However, when we do this in different orders, we can get different
> results. We were processing the uses on is_gimple_debug statements just
> like normal uses, and this would sometimes cause a difference in how
> things were resolved.
>
> This patch adds a flag to enable/disable this attempt to look up new
> values, and when range_of_expr is processing the use on a debug
> statement, turns it off for the query. This means the query will never
> cause a new lookup, and this should resolve all the -fcompare-debug issues.
>
> Bootstrapped on x86_64-pc-linux-gnu, with no new regressions. Pushed.
Please check if such fixes also apply to the GCC 11 branch.
Richard.
> Andrew
>
next prev parent reply other threads:[~2021-06-01 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 1:32 Andrew MacLeod
2021-06-01 7:34 ` Richard Biener [this message]
2021-06-01 14:23 ` Andrew MacLeod
2021-06-02 7:29 ` Richard Biener
2021-06-08 14:48 ` Andrew MacLeod
2021-06-09 11:48 ` Richard Biener
2021-06-09 15:24 ` Andrew MacLeod
2021-06-10 5:59 ` 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='CAFiYyc2wUhFMP5Xy9e=USDfLbTjUbROTdkG0ka=8wvh9TcdzDQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@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).