public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: Monk Chiang <monk.chiang@sifive.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Add type attribute for atomic instructions.
Date: Fri, 21 Oct 2022 15:35:04 +0800	[thread overview]
Message-ID: <CA+yXCZAhphcJLQWfpq3ngLYFF9EoK9AnsxYzfrz8vTPQNv9BAA@mail.gmail.com> (raw)
In-Reply-To: <20221021050159.121335-1-monk.chiang@sifive.com>

Committed, thanks :)

On Fri, Oct 21, 2022 at 1:02 PM Monk Chiang <monk.chiang@sifive.com> wrote:
>
> gcc/ChangeLog:
>
>         * config/riscv/riscv.md: Add atomic type attribute.
>         * config/riscv/sync.md: Add atomic type for atomic instructions.
> ---
>  gcc/config/riscv/riscv.md |  2 +-
>  gcc/config/riscv/sync.md  | 15 ++++++++++-----
>  2 files changed, 11 insertions(+), 6 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv.md b/gcc/config/riscv/riscv.md
> index b3654915fde..9384ced0447 100644
> --- a/gcc/config/riscv/riscv.md
> +++ b/gcc/config/riscv/riscv.md
> @@ -317,7 +317,7 @@
>    "unknown,branch,jump,call,load,fpload,store,fpstore,
>     mtc,mfc,const,arith,logical,shift,slt,imul,idiv,move,fmove,fadd,fmul,
>     fmadd,fdiv,fcmp,fcvt,fsqrt,multi,auipc,sfb_alu,nop,ghost,bitmanip,rotate,
> -   rdvlenb,rdvl,vsetvl,vlde,vste,vldm,vstm,vlds,vsts,
> +   atomic,rdvlenb,rdvl,vsetvl,vlde,vste,vldm,vstm,vlds,vsts,
>     vldux,vldox,vstux,vstox,vldff,vldr,vstr,
>     vialu,viwalu,vext,vicalu,vshift,vnshift,vicmp,
>     vimul,vidiv,viwmul,vimuladd,viwmuladd,vimerge,vimov,
> diff --git a/gcc/config/riscv/sync.md b/gcc/config/riscv/sync.md
> index 7deb290d9dc..449f275e6a2 100644
> --- a/gcc/config/riscv/sync.md
> +++ b/gcc/config/riscv/sync.md
> @@ -62,7 +62,8 @@
>        UNSPEC_ATOMIC_STORE))]
>    "TARGET_ATOMIC"
>    "%F2amoswap.<amo>%A2 zero,%z1,%0"
> -  [(set (attr "length") (const_int 8))])
> +  [(set_attr "type" "atomic")
> +   (set (attr "length") (const_int 8))])
>
>  (define_insn "atomic_<atomic_optab><mode>"
>    [(set (match_operand:GPR 0 "memory_operand" "+A")
> @@ -73,7 +74,8 @@
>          UNSPEC_SYNC_OLD_OP))]
>    "TARGET_ATOMIC"
>    "%F2amo<insn>.<amo>%A2 zero,%z1,%0"
> -  [(set (attr "length") (const_int 8))])
> +  [(set_attr "type" "atomic")
> +   (set (attr "length") (const_int 8))])
>
>  (define_insn "atomic_fetch_<atomic_optab><mode>"
>    [(set (match_operand:GPR 0 "register_operand" "=&r")
> @@ -86,7 +88,8 @@
>          UNSPEC_SYNC_OLD_OP))]
>    "TARGET_ATOMIC"
>    "%F3amo<insn>.<amo>%A3 %0,%z2,%1"
> -  [(set (attr "length") (const_int 8))])
> +  [(set_attr "type" "atomic")
> +   (set (attr "length") (const_int 8))])
>
>  (define_insn "atomic_exchange<mode>"
>    [(set (match_operand:GPR 0 "register_operand" "=&r")
> @@ -98,7 +101,8 @@
>         (match_operand:GPR 2 "register_operand" "0"))]
>    "TARGET_ATOMIC"
>    "%F3amoswap.<amo>%A3 %0,%z2,%1"
> -  [(set (attr "length") (const_int 8))])
> +  [(set_attr "type" "atomic")
> +   (set (attr "length") (const_int 8))])
>
>  (define_insn "atomic_cas_value_strong<mode>"
>    [(set (match_operand:GPR 0 "register_operand" "=&r")
> @@ -112,7 +116,8 @@
>     (clobber (match_scratch:GPR 6 "=&r"))]
>    "TARGET_ATOMIC"
>    "%F5 1: lr.<amo>%A5 %0,%1; bne %0,%z2,1f; sc.<amo>%A4 %6,%z3,%1; bnez %6,1b; 1:"
> -  [(set (attr "length") (const_int 20))])
> +  [(set_attr "type" "atomic")
> +   (set (attr "length") (const_int 20))])
>
>  (define_expand "atomic_compare_and_swap<mode>"
>    [(match_operand:SI 0 "register_operand" "")   ;; bool output
> --
> 2.37.2
>

      reply	other threads:[~2022-10-21  7:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  5:01 Monk Chiang
2022-10-21  7:35 ` Kito Cheng [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=CA+yXCZAhphcJLQWfpq3ngLYFF9EoK9AnsxYzfrz8vTPQNv9BAA@mail.gmail.com \
    --to=kito.cheng@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=monk.chiang@sifive.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).