From: Jeff Law <jlaw@ventanamicro.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] Minor cleanup/prep in DOM
Date: Fri, 30 Sep 2022 18:50:31 -0600 [thread overview]
Message-ID: <873b545e-d30c-4797-f467-ccff8644b54d@ventanamicro.com> (raw)
In-Reply-To: <CAMe9rOoq1C_QEf=as9HV6EQbj+g00M1CjDZR2TDbPC5FSbXhug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On 9/30/22 18:07, H.J. Lu wrote:
> On Fri, Sep 30, 2022 at 4:06 PM Jeff Law <jlaw@ventanamicro.com> wrote:
>>
>> It's a bit weird that free_dom_edge_info leaves a dangling pointer in
>> e->aux. Not sure what I was thinking.
>>
>>
>> There's two callers. One wipes e->aux immediately after the call, the
>> other attaches a newly created object immediately after the call. So we
>> can wipe e->aux within the call and simplify one of the two call sites.
>>
>> This is preparatory work for a minor optimization where we want to
>> detect another class of edge equivalences in DOM (until something better
>> is available) and either attach them an existing edge_info structure or
>> create a new one if one doesn't currently exist for a given edge.
>>
>> Bootstrapped and regression tested on x86_64. Installing on the trunk.
>>
> I got
[ ... ]
Pushed wrong version. Sorry about that. Fixed by attached patch which
just moves the test down to its proper position.
Jeff
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 1356 bytes --]
commit aa360fbf68b11e54017e8fa5b1bdb87ce7c19188
Author: Jeff Law <jeffreyalaw@gmail.com>
Date: Fri Sep 30 20:46:04 2022 -0400
Install correct patch version.
gcc/
* tree-ssa-dom.cc (record_edge_info): Install correct version of
patch.
diff --git a/gcc/tree-ssa-dom.cc b/gcc/tree-ssa-dom.cc
index 8d8312ca350..e6b8dace5e9 100644
--- a/gcc/tree-ssa-dom.cc
+++ b/gcc/tree-ssa-dom.cc
@@ -684,11 +684,6 @@ record_edge_info (basic_block bb)
!gsi_end_p (gsi);
gsi_next (&gsi))
{
- /* If the other alternative is the same as the result,
- then this is a degenerate and can be ignored. */
- if (dst == PHI_ARG_DEF (phi, !alternative))
- continue;
-
/* Now get the EDGE_INFO class so we can append
it to our list. We want the successor edge
where the destination is not the source of
@@ -697,6 +692,11 @@ record_edge_info (basic_block bb)
tree src = PHI_ARG_DEF (phi, alternative);
tree dst = PHI_RESULT (phi);
+ /* If the other alternative is the same as the result,
+ then this is a degenerate and can be ignored. */
+ if (dst == PHI_ARG_DEF (phi, !alternative))
+ continue;
+
if (EDGE_SUCC (bb, 0)->dest
!= EDGE_PRED (bb, !alternative)->src)
edge_info = (class edge_info *)EDGE_SUCC (bb, 0)->aux;
prev parent reply other threads:[~2022-10-01 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 23:05 Jeff Law
2022-10-01 0:07 ` H.J. Lu
2022-10-01 0:50 ` Jeff Law [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=873b545e-d30c-4797-f467-ccff8644b54d@ventanamicro.com \
--to=jlaw@ventanamicro.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@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).