From: Jeff Law <law@redhat.com>
To: "Bin.Cheng" <amker.cheng@gmail.com>,
Richard Biener <richard.guenther@gmail.com>
Cc: Bin Cheng <Bin.Cheng@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH PR68030/PR69710][RFC]Introduce a simple local CSE interface and use it in vectorizer
Date: Tue, 21 Jun 2016 21:58:00 -0000 [thread overview]
Message-ID: <67f669fe-83f4-1c38-513d-8b9383f18ed9@redhat.com> (raw)
In-Reply-To: <CAHFci2_CH1Fg3xmrOyc98xMbdEUzeJTkweJtBVMPkoAqqRtRxw@mail.gmail.com>
On 06/06/2016 05:23 AM, Bin.Cheng wrote:
> Hi Jeff,
> What's your opinion on this (and how to extend it to a region based
> interface)? I will update this patch for further review if you are
> okay.
I've never pondered how to revamp DOM into a regional interface (though
I have pondered how to revamp the threading bits into a regional
interface -- without any real success).
Conceptually I think it's just a matter of setting an entry block/edge,
computing all blocks dominated by that entry block/edge and limiting the
walker to only visiting blocks in that set. So the regional aspect
would live in domwalk.[ch].
We'd probably want to avoid all the threading bits in a regional walk --
not because threading isn't useful, but sequencing the updates is a PITA
and trying to do it in the middle of some other pass would just be a mess.
jeff
next prev parent reply other threads:[~2016-06-21 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 13:03 Bin Cheng
2016-05-27 12:07 ` Richard Biener
2016-05-27 12:15 ` Bin.Cheng
2016-05-27 13:01 ` Richard Biener
2016-06-06 11:23 ` Bin.Cheng
2016-06-21 21:58 ` Jeff Law [this message]
2016-06-21 21:54 ` Jeff Law
2016-07-13 20:59 ` Jeff Law
2016-11-21 21:34 ` Doug Gilmore
2016-11-22 16:07 ` Bin.Cheng
2016-11-23 0:35 ` Doug Gilmore
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=67f669fe-83f4-1c38-513d-8b9383f18ed9@redhat.com \
--to=law@redhat.com \
--cc=Bin.Cheng@arm.com \
--cc=amker.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@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).