From: Jiong Wang <wong.kwongyuan.tools@gmail.com>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>
Cc: Jeff Law <law@redhat.com>,
Steven Bosscher <stevenb.gcc@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: Tue, 28 Apr 2015 14:31:00 -0000 [thread overview]
Message-ID: <CAAfDdZ2nq-=y=S=Vq=aDZD9mnnkvfmDvT-Du6_Zkc+_bxH-9rw@mail.gmail.com> (raw)
In-Reply-To: <6D39441BF12EF246A7ABCE6654B0235321041BEF@LEMAIL01.le.imgtec.org>
2015-04-28 14:56 GMT+01:00 Matthew Fortune <Matthew.Fortune@imgtec.com>:
>> Hi Matthew,
>>
>> 2015-04-21 15:24 GMT+01:00 Jiong Wang <jiong.wang@arm.com>:
>>
>> >
>> > 2015-04-21 Jiong Wang <jiong.wang@arm.com>
>> >
>> > gcc/
>> > * loop-invariant.c (find_defs): Enable DF_DU_CHAIN build.
>> > (vfp_const_iv): New hash table.
>> > (expensive_addr_check_p): New boolean.
>> > (init_inv_motion_data): Initialize new variables.>
>> > (free_inv_motion_data): Release hash table.
>> > (create_new_invariant): Set cheap_address to false for iv in
>> > vfp_const_iv table.
>> > (find_invariant_insn): Skip dependencies check for iv in
>> vfp_const_iv
>> > table.
>> > (use_for_single_du): New function.
>> > (reshuffle_insn_with_vfp): Likewise.
>> > (find_invariants_bb): Call reshuffle_insn_with_vfp.
>>
>> Is it possible for you to test this patch on spec2k6 on MIPS?
>> especially 436.cactusADM.
>> I am interested in the performance impact on other load/store machines.
>
> I will certainly try and fit it in. It may take me a week to get back to
> you though as I'm away on vacation for a few days.
Thanks very much. I appreciate that.
And you can add "-fdump-rtl-loop2_invariant", then we can see how many
new loop invariants found at RTL level across spec2k6 on MIPS.
Thanks.
Regards,
Jiong
next prev parent reply other threads:[~2015-04-28 14:00 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
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 [this message]
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='CAAfDdZ2nq-=y=S=Vq=aDZD9mnnkvfmDvT-Du6_Zkc+_bxH-9rw@mail.gmail.com' \
--to=wong.kwongyuan.tools@gmail.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=stevenb.gcc@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).