From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jiong Wang <jiong.wang@arm.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR 62173, re-shuffle insns for RTL loop invariant hoisting
Date: Thu, 18 Dec 2014 22:19:00 -0000 [thread overview]
Message-ID: <20141218220908.GA20720@gate.crashing.org> (raw)
In-Reply-To: <54930811.1020003@arm.com>
On Thu, Dec 18, 2014 at 05:00:01PM +0000, Jiong Wang wrote:
> On 17/12/14 15:54, Richard Biener wrote:
> >ick. I realize we don't have SSA form on RTL but doesn't DF provide
> >at least some help in looking up definition statements for pseudos?
> >In fact we want to restrict the transform to single-use pseudos, thus
> >hopefully it can at least tell us that... (maybe not and this is what
> >LOG_LINKS are for in combine...?) At least loop-invariant alreadly
> >computes df_chain with DF_UD_CHAIN which seems exactly what
> >is needed (apart from maybe getting at single-use info).
>
> thanks very much for these inspiring questions.
>
> yes, we want to restrict the transformation on single-use pseudo only,
> and it's better the transformation could re-use existed info and helper
> function to avoid increase compile time. but I haven't found anything I
> can reuse at the stage the transformation happen.
>
> the info similar as LOG_LINKS is what I want, but maybe simpler. I'd study
> the code about build LOG_LINKS, and try to see if we can do some factor out.
LOG_LINKs in combine are just historical. combine should be converted
to use DF fully.
LOG_LINKs have nothing to do with single use; they point from the _first_
use to its corresponding def.
You might want to look at what fwprop does instead.
Segher
next prev parent reply other threads:[~2014-12-18 22:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 11:00 Jiong Wang
2014-12-04 11:07 ` Richard Biener
2014-12-04 11:07 ` Richard Biener
2014-12-04 19:32 ` Jiong Wang
2014-12-15 15:29 ` Jiong Wang
2014-12-15 15:36 ` Jiong Wang
2014-12-17 16:19 ` Richard Biener
2014-12-18 17:08 ` Jiong Wang
2014-12-18 21:16 ` Jiong Wang
2014-12-18 22:19 ` Segher Boessenkool [this message]
2014-12-19 4:06 ` Bin.Cheng
2014-12-19 10:29 ` Jiong Wang
2014-12-19 11:45 ` Richard Biener
2014-12-19 15:31 ` Kenneth Zadeck
2015-02-11 11:20 ` Jiong Wang
2015-02-11 14:22 ` Kenneth Zadeck
2015-02-11 18:18 ` Jiong Wang
2015-04-14 15:06 ` Jiong Wang
2015-04-14 16:49 ` Steven Bosscher
2015-04-14 17:24 ` Jeff Law
2015-04-14 21:49 ` Jiong Wang
2015-04-21 14:43 ` Jiong Wang
2015-04-24 1:55 ` Jeff Law
2015-04-24 17:05 ` Jiong Wang
2015-05-14 20:04 ` Jeff Law
2015-05-14 22:07 ` Jiong Wang
2015-05-14 22:24 ` Jeff Law
2015-05-21 21:51 ` Jiong Wang
2015-05-27 16:11 ` Jeff Law
2015-09-02 13:49 ` Jiong Wang
2015-09-02 20:52 ` Jeff Law
2015-04-28 12:16 ` Jiong Wang
2015-04-28 14:00 ` Matthew Fortune
2015-04-28 14:31 ` Jiong Wang
2015-04-19 16:20 ` Jiong Wang
2014-12-19 12:09 ` Eric Botcazou
2014-12-19 15:21 ` Segher Boessenkool
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=20141218220908.GA20720@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiong.wang@arm.com \
--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).