public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Die Li <lidie@eswincomputing.com>, gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, palmer@dabbelt.com
Subject: Re: [PATCH] RISC-V: Optimize TARGET_XTHEADCONDMOV
Date: Mon, 29 May 2023 11:14:34 -0600	[thread overview]
Message-ID: <b7850622-f5e4-f805-34a1-af036d47b962@gmail.com> (raw)
In-Reply-To: <20230526005240.86495-1-lidie@eswincomputing.com>



On 5/25/23 18:52, Die Li wrote:
> This patch allows less instructions to be used when TARGET_XTHEADCONDMOV is enabled.
> 
> Provide an example from the existing testcases.
> 
> Testcase:
> int ConEmv_imm_imm_reg(int x, int y){
>    if (x == 1000) return 10;
>    return y;
> }
> 
> Cflags:
> -O2 -march=rv64gc_xtheadcondmov -mabi=lp64d
> 
> before patch:
> ConEmv_imm_imm_reg:
> 	addi	a5,a0,-1000
> 	li	a0,10
> 	th.mvnez	a0,zero,a5
> 	th.mveqz	a1,zero,a5
> 	or	a0,a0,a1
> 	ret
> 
> after patch:
> ConEmv_imm_imm_reg:
> 	addi	a5,a0,-1000
> 	li	a0,10
> 	th.mvnez	a0,a1,a5
> 	ret
> 
> Signed-off-by: Die Li <lidie@eswincomputing.com>
> 
> gcc/ChangeLog:
> 
>          * config/riscv/riscv.cc (riscv_expand_conditional_move_onesided): Delete.
>          (riscv_expand_conditional_move):  Reuse the TARGET_SFB_ALU expand process for TARGET_XTHEADCONDMOV
> 
> gcc/testsuite/ChangeLog:
> 
>          * gcc.target/riscv/xtheadcondmov-indirect-rv32.c: Update the output.
>          * gcc.target/riscv/xtheadcondmov-indirect-rv64.c: Likewise.
I've made minor formatting adjustments and pushed this to the trunk.


> @@ -3492,14 +3462,12 @@ riscv_expand_conditional_move (rtx dest, rtx op, rtx cons, rtx alt)
>         && GET_MODE (op0) == mode
>         && GET_MODE (op1) == mode
>         && (code == EQ || code == NE))
> +        need_eq_ne_p = true;
So the need_eq_ne_p should have indented 2 spaces in from the IF statement.

> +
> +  if (need_eq_ne_p || (TARGET_SFB_ALU
> +	   && GET_MODE (op0) == word_mode))This should have been:
   if (need_eq_ne_p
       || (TARGET_SFB_ALU && GET_MODE (op0) == word_mode))

I've fixed this as well.

I would recommend you review the GCC coding guidelines.  While I fixed 
the problems this time, I'll likely ask you to do so in the future.

jeff

      parent reply	other threads:[~2023-05-29 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26  0:52 Die Li
2023-05-26  2:43 ` Kito Cheng
2023-05-26  4:01   ` Jeff Law
2023-05-26  8:20 ` Philipp Tomsich
2023-05-29 17:14 ` Jeff Law [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=b7850622-f5e4-f805-34a1-af036d47b962@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kito.cheng@gmail.com \
    --cc=lidie@eswincomputing.com \
    --cc=palmer@dabbelt.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).