From: luoxhu <luoxhu@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org, wschmidt@linux.ibm.com,
guojiufu@linux.ibm.com, linkw@gcc.gnu.org
Subject: Re: [PATCH] rs6000: Don't split constant oprator when add, move to temp register for future optimization
Date: Mon, 30 Mar 2020 11:59:57 +0800 [thread overview]
Message-ID: <388143a3-7889-0476-abd7-d2e9b667e5f4@linux.ibm.com> (raw)
In-Reply-To: <20200327143331.GD22482@gate.crashing.org>
On 2020/3/27 22:33, Segher Boessenkool wrote:
> Hi!
>
> On Thu, Mar 26, 2020 at 05:06:43AM -0500, luoxhu@linux.ibm.com wrote:
>> Remove split code from add<mode>3 to allow a later pass to split.
>> This allows later logic to hoist out constant load in add instructions.
>> In loop, lis+ori could be hoisted out to improve performance compared with
>> previous addis+addi (About 15% on typical case), weak point is
>> one more register is used and one more instruction is generated. i.e.:
>>
>> addis 3,3,0x8765
>> addi 3,3,0x4321
>>
>> =>
>>
>> lis 9,0x8765
>> ori 9,9,0x4321
>> add 3,3,9
>
> What does it do overall? Say, to SPEC. What does it do to execution
> time, and what does it do to binary size?
>
> Do we want something later in the RTL pipeline to make "addi"s etc. again?
>
>> 2020-03-26 Xiong Hu Luo <luoxhu@linux.ibm.com>
>>
>> * config/rs6000/rs6000.md (add<mode>3): Remove split code, move constant
>> to temp register before add.
>
> This should not be indented, so just:
> * config/rs6000/rs6000.md (add<mode>3): Remove split code, move constant
> to temp register before add.
>
> We have six separate add<mode>3 patterns (three of those are in rs6000.md,
> too). You can write something like
> (add<mode>3 for SDI):
> to show which iterator (or mode) this one is for. This is helpful with
> any <mode> or <code> or the like, even if there (currently) is only one
> pattern you could mean.
>
Thanks, it is necessary to re-enable split add as some later RTL passes like final will
still need generate addis+addi (case: g++.dg/opt/thunk1.C ).
Update the patch as below:
[PATCH] rs6000: Don't split constant operator add before reload, move to temp register for future optimization
Don't split code from add<mode>3 for SDI to allow a later pass to split.
This allows later logic to hoist out constant load in add instructions.
In loop, lis+ori could be hoisted out to improve performance compared with
previous addis+addi (About 15% on typical case), weak point is
one more register is used and one more instruction is generated. i.e.:
addis 3,3,0x8765
addi 3,3,0x4321
=>
lis 9,0x8765
ori 9,9,0x4321
add 3,3,9
No obvious performance and binary size change to SPEC2017.
gcc/ChangeLog:
2020-03-30 Xiong Hu Luo <luoxhu@linux.ibm.com>
* config/rs6000/rs6000.md (add<mode>3 for SDI): Don't split before reload,
move constant to temp register for add.
gcc/testsuite/ChangeLog:
2020-03-26 Xiong Hu Luo <luoxhu@linux.ibm.com>
* gcc.target/powerpc/add-const.c: New.
---
gcc/config/rs6000/rs6000.md | 51 +++++++++-----------
gcc/testsuite/gcc.target/powerpc/add-const.c | 18 +++++++
2 files changed, 42 insertions(+), 27 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/powerpc/add-const.c
diff --git a/gcc/config/rs6000/rs6000.md b/gcc/config/rs6000/rs6000.md
index ad88b6783af..76af3d5b1d9 100644
--- a/gcc/config/rs6000/rs6000.md
+++ b/gcc/config/rs6000/rs6000.md
@@ -1729,34 +1729,31 @@ (define_expand "add<mode>3"
if (CONST_INT_P (operands[2]) && !add_operand (operands[2], <MODE>mode))
{
- rtx tmp = ((!can_create_pseudo_p ()
- || rtx_equal_p (operands[0], operands[1]))
- ? operands[0] : gen_reg_rtx (<MODE>mode));
-
- /* Adding a constant to r0 is not a valid insn, so use a different
- strategy in that case. */
- if (reg_or_subregno (operands[1]) == 0 || reg_or_subregno (tmp) == 0)
- {
- if (operands[0] == operands[1])
- FAIL;
- rs6000_emit_move (operands[0], operands[2], <MODE>mode);
- emit_insn (gen_add<mode>3 (operands[0], operands[1], operands[0]));
- DONE;
- }
-
- HOST_WIDE_INT val = INTVAL (operands[2]);
- HOST_WIDE_INT low = ((val & 0xffff) ^ 0x8000) - 0x8000;
- HOST_WIDE_INT rest = trunc_int_for_mode (val - low, <MODE>mode);
-
- if (<MODE>mode == DImode && !satisfies_constraint_L (GEN_INT (rest)))
- FAIL;
+ if (can_create_pseudo_p ())
+ {
+ rtx tmp = rtx_equal_p (operands[0], operands[1])
+ ? operands[0] : gen_reg_rtx (<MODE>mode);
- /* The ordering here is important for the prolog expander.
- When space is allocated from the stack, adding 'low' first may
- produce a temporary deallocation (which would be bad). */
- emit_insn (gen_add<mode>3 (tmp, operands[1], GEN_INT (rest)));
- emit_insn (gen_add<mode>3 (operands[0], tmp, GEN_INT (low)));
- DONE;
+ rs6000_emit_move (tmp, operands[2], <MODE>mode);
+ emit_insn (gen_add<mode>3 (operands[0], operands[1], tmp));
+ DONE;
+ }
+ else
+ {
+ HOST_WIDE_INT val = INTVAL (operands[2]);
+ HOST_WIDE_INT low = ((val & 0xffff) ^ 0x8000) - 0x8000;
+ HOST_WIDE_INT rest = trunc_int_for_mode (val - low, <MODE>mode);
+
+ if (<MODE>mode == DImode && !satisfies_constraint_L (GEN_INT (rest)))
+ FAIL;
+
+ /* The ordering here is important for the prolog expander.
+ When space is allocated from the stack, adding 'low' first may
+ produce a temporary deallocation (which would be bad). */
+ emit_insn (gen_add<mode>3 (operands[0], operands[1], GEN_INT (rest)));
+ emit_insn (gen_add<mode>3 (operands[0], operands[0], GEN_INT (low)));
+ DONE;
+ }
}
})
diff --git a/gcc/testsuite/gcc.target/powerpc/add-const.c b/gcc/testsuite/gcc.target/powerpc/add-const.c
new file mode 100644
index 00000000000..e1007247b32
--- /dev/null
+++ b/gcc/testsuite/gcc.target/powerpc/add-const.c
@@ -0,0 +1,18 @@
+/* { dg-do compile { target { lp64 } } } */
+/* { dg-options "-O3 -fno-unroll-loops" } */
+
+/* Ensure the lis,ori are generated, which indicates they have
+ been hoisted outside of the loop. */
+
+typedef unsigned long ulong;
+ulong
+foo (ulong n, ulong h)
+{
+ int i;
+ for (i = 0; i < n; i++)
+ h = ((h + 8) | h) + 0x87654321;
+ return h;
+}
+
+/* { dg-final { scan-assembler-times {\mlis\M} 1 } } */
+/* { dg-final { scan-assembler-times {\mori\M} 1 } } */
--
2.21.0.777.g83232e3864
next prev parent reply other threads:[~2020-03-30 4:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 10:06 luoxhu
2020-03-26 15:18 ` will schmidt
2020-03-27 14:33 ` Segher Boessenkool
2020-03-30 3:59 ` luoxhu [this message]
2020-04-02 22:16 ` Segher Boessenkool
2020-04-03 6:13 ` luoxhu
2020-04-03 12:13 ` Alan Modra
2020-04-03 21:11 ` Segher Boessenkool
2020-04-03 23:51 ` Alan Modra
2020-04-07 21:47 ` Segher Boessenkool
2020-04-03 21:08 ` 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=388143a3-7889-0476-abd7-d2e9b667e5f4@linux.ibm.com \
--to=luoxhu@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=linkw@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.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).