From: Max Filippov <jcmvbkbc@gmail.com>
To: "Takayuki 'January June' Suwa" <jjsuwa_sys3175@yahoo.co.jp>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2] xtensa: Optimize '(x & CST1_POW2) != 0 ? CST2_POW2 : 0'
Date: Tue, 23 May 2023 13:05:12 -0700 [thread overview]
Message-ID: <CAMo8BfJiZNOdFP+-YL6D4PZPfZxq34pv19u4dwLWBeELuShTjg@mail.gmail.com> (raw)
In-Reply-To: <5b04c828-7906-2efb-a834-d3ed0ba1f6bd@yahoo.co.jp>
On Mon, May 22, 2023 at 10:48 PM Takayuki 'January June' Suwa
<jjsuwa_sys3175@yahoo.co.jp> wrote:
>
> On 2023/05/23 11:27, Max Filippov wrote:
> > Hi Suwa-san,
>
> Hi!
>
> > This change introduces a bunch of test failures on big endian configuration.
> > I believe that's because the starting bit position for zero_extract is counted
> > from different ends depending on the endianness.
>
> Oops, what a stupid mistake... X(
>
> ===
> This patch decreses one machine instruction from "single bit extraction
> with shifting" operation, and tries to eliminate the conditional
> branch if CST2_POW2 doesn't fit into signed 12 bits with the help
> of ifcvt optimization.
>
> /* example #1 */
> int test0(int x) {
> return (x & 1048576) != 0 ? 1024 : 0;
> }
> extern int foo(void);
> int test1(void) {
> return (foo() & 1048576) != 0 ? 16777216 : 0;
> }
>
> ;; before
> test0:
> movi a9, 0x400
> srai a2, a2, 10
> and a2, a2, a9
> ret.n
> test1:
> addi sp, sp, -16
> s32i.n a0, sp, 12
> call0 foo
> extui a2, a2, 20, 1
> slli a2, a2, 20
> beqz.n a2, .L2
> movi.n a2, 1
> slli a2, a2, 24
> .L2:
> l32i.n a0, sp, 12
> addi sp, sp, 16
> ret.n
>
> ;; after
> test0:
> extui a2, a2, 20, 1
> slli a2, a2, 10
> ret.n
> test1:
> addi sp, sp, -16
> s32i.n a0, sp, 12
> call0 foo
> l32i.n a0, sp, 12
> extui a2, a2, 20, 1
> slli a2, a2, 24
> addi sp, sp, 16
> ret.n
>
> In addition, if the left shift amount ('exact_log2(CST2_POW2)') is
> between 1 through 3 and a either addition or subtraction with another
> register follows, emit a ADDX[248] or SUBX[248] machine instruction
> instead of separate left shift and add/subtract ones.
>
> /* example #2 */
> int test2(int x, int y) {
> return ((x & 1048576) != 0 ? 4 : 0) + y;
> }
> int test3(int x, int y) {
> return ((x & 2) != 0 ? 8 : 0) - y;
> }
>
> ;; before
> test2:
> movi.n a9, 4
> srai a2, a2, 18
> and a2, a2, a9
> add.n a2, a2, a3
> ret.n
> test3:
> movi.n a9, 8
> slli a2, a2, 2
> and a2, a2, a9
> sub a2, a2, a3
> ret.n
>
> ;; after
> test2:
> extui a2, a2, 20, 1
> addx4 a2, a2, a3
> ret.n
> test3:
> extui a2, a2, 1, 1
> subx8 a2, a2, a3
> ret.n
>
> gcc/ChangeLog:
>
> * config/xtensa/predicates.md (addsub_operator): New.
> * config/xtensa/xtensa.md (*extzvsi-1bit_ashlsi3,
> *extzvsi-1bit_addsubx): New insn_and_split patterns.
> * config/xtensa/xtensa.cc (xtensa_rtx_costs):
> Add a special case about ifcvt 'noce_try_cmove()' to handle
> constant loads that do not fit into signed 12 bits in the
> patterns added above.
> ---
> gcc/config/xtensa/predicates.md | 3 ++
> gcc/config/xtensa/xtensa.cc | 3 +-
> gcc/config/xtensa/xtensa.md | 83 +++++++++++++++++++++++++++++++++
> 3 files changed, 88 insertions(+), 1 deletion(-)
Regtested for target=xtensa-linux-uclibc, no new regressions.
Committed to master.
--
Thanks.
-- Max
prev parent reply other threads:[~2023-05-23 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ea701092-71a1-7c4b-3070-376f9421252c.ref@yahoo.co.jp>
2023-05-22 7:03 ` [PATCH 1/2] " Takayuki 'January June' Suwa
2023-05-23 2:27 ` Max Filippov
2023-05-23 2:37 ` Andrew Pinski
2023-05-23 5:48 ` [PATCH v2] " Takayuki 'January June' Suwa
2023-05-23 20:05 ` Max Filippov [this message]
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=CAMo8BfJiZNOdFP+-YL6D4PZPfZxq34pv19u4dwLWBeELuShTjg@mail.gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jjsuwa_sys3175@yahoo.co.jp \
/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).