From: Jeff Law <jeffreyalaw@gmail.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Kito Cheng <kito.cheng@gmail.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/1] RISC-V: Make "prefetch.i" built-in usable
Date: Mon, 28 Aug 2023 15:20:59 -0600 [thread overview]
Message-ID: <5b7219c9-76d6-574b-a7e4-2e0992a56198@gmail.com> (raw)
In-Reply-To: <97c0d824fa5aeaee52a825da7f7a17ae8616c5ab.1691636916.git.research_trasio@irq.a4lg.com>
On 8/9/23 21:10, Tsukasa OI via Gcc-patches wrote:
> From: Tsukasa OI <research_trasio@irq.a4lg.com>
>
> The "__builtin_riscv_zicbop_cbo_prefetchi" built-in function was terribly
> broken so that practically unusable. It emitted "prefetch.i" but with no
> meaningful arguments.
>
> Though incompatible, this commit completely changes the function prototype
> of this built-in and makes it usable. To minimize the functionality issues,
> it renames the built-in to "__builtin_riscv_zicbop_prefetch_i".
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-cmo.def: Fix function prototype.
> * config/riscv/riscv.md (riscv_prefetchi_<mode>): Fix instruction
> prototype. Remove possible prefectch type argument
> * doc/extend.texi: Document __builtin_riscv_zicbop_prefetch_i.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/cmo-zicbop-1.c: Reflect new built-in prototype.
> * gcc.target/riscv/cmo-zicbop-2.c: Likewise.
> diff --git a/gcc/config/riscv/riscv.md b/gcc/config/riscv/riscv.md
> index 688fd697255b..5658c7b7e113 100644
> --- a/gcc/config/riscv/riscv.md
> +++ b/gcc/config/riscv/riscv.md
> @@ -3273,9 +3273,8 @@
> })
>
> (define_insn "riscv_prefetchi_<mode>"
> - [(unspec_volatile:X [(match_operand:X 0 "address_operand" "r")
> - (match_operand:X 1 "imm5_operand" "i")]
> - UNSPECV_PREI)]
> + [(unspec_volatile:X [(match_operand:X 0 "register_operand" "r")]
> + UNSPECV_PREI)]
> "TARGET_ZICBOP"
> "prefetch.i\t%a0"
> )
What I would suggest is making a new predicate that accepts either a
register or a register+offset where the offset fits in a signed 12 bit
immediate. Use that for operand 0's predicate and I think this will
"just work" and cover all the cases supported by the prefetch.i instruction.
Jeff
next prev parent reply other threads:[~2023-08-28 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 3:10 [PATCH 0/1] " Tsukasa OI
2023-08-10 3:10 ` [PATCH 1/1] " Tsukasa OI
2023-08-28 21:20 ` Jeff Law [this message]
2023-08-29 2:09 ` Tsukasa OI
2023-08-29 13:47 ` Jeff Law
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=5b7219c9-76d6-574b-a7e4-2e0992a56198@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=research_trasio@irq.a4lg.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).