public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Support (set (mem) (const_poly_int))
Date: Mon, 24 Oct 2022 10:50:29 +0800	[thread overview]
Message-ID: <CA+yXCZBpQTcECVbR7zrbampttOwUFq3s2xswyrEDqh==2P=v7w@mail.gmail.com> (raw)
In-Reply-To: <20221024022737.52627-1-juzhe.zhong@rivai.ai>

Merged two changes into one patch, and committed to master :)

On Mon, Oct 24, 2022 at 10:28 AM <juzhe.zhong@rivai.ai> wrote:
>
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> gcc/ChangeLog:
>
>         * config/riscv/riscv.cc (riscv_legitimize_move): Adjust using force_reg.
>
> ---
>  gcc/config/riscv/riscv.cc | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
> index 98374a922d1..1fd34f6ae8d 100644
> --- a/gcc/config/riscv/riscv.cc
> +++ b/gcc/config/riscv/riscv.cc
> @@ -1967,9 +1967,7 @@ riscv_legitimize_move (machine_mode mode, rtx dest, rtx src)
>        */
>        if (MEM_P (dest))
>         {
> -         rtx tmp = gen_reg_rtx (mode);
> -         emit_move_insn (tmp, src);
> -         emit_move_insn (dest, tmp);
> +         emit_move_insn (dest, force_reg (mode, src));
>           return true;
>         }
>        poly_int64 value = rtx_to_poly_int64 (src);
> --
> 2.36.1
>

  reply	other threads:[~2022-10-24  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  2:27 juzhe.zhong
2022-10-24  2:50 ` Kito Cheng [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-24  2:03 juzhe.zhong
2022-10-24  2:14 ` Andrew Pinski

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='CA+yXCZBpQTcECVbR7zrbampttOwUFq3s2xswyrEDqh==2P=v7w@mail.gmail.com' \
    --to=kito.cheng@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    /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).