From: Segher Boessenkool <segher@kernel.crashing.org>
To: luoxhu <luoxhu@linux.ibm.com>
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: Thu, 2 Apr 2020 17:16:53 -0500 [thread overview]
Message-ID: <20200402221653.GG26902@gate.crashing.org> (raw)
In-Reply-To: <388143a3-7889-0476-abd7-d2e9b667e5f4@linux.ibm.com>
Hi!
On Mon, Mar 30, 2020 at 11:59:57AM +0800, luoxhu wrote:
> > Do we want something later in the RTL pipeline to make "addi"s etc. again?
(This would be a good thing to consider -- maybe a define_insn_and_split
will work. But see 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
(This patch will of course have to wait for stage 1).
Such a define_insn_and_split could be for an add of a (signed) 32-bit
immediate. combine will try to combine the three insns (lis;ori;add),
and match the new pattern.
This also links in with Alan's work on big immediates, and with paddi
insns, etc.
Segher
next prev parent reply other threads:[~2020-04-02 22:16 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
2020-04-02 22:16 ` Segher Boessenkool [this message]
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=20200402221653.GG26902@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=linkw@gcc.gnu.org \
--cc=luoxhu@linux.ibm.com \
--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).