public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Robin Dapp <rdapp.gcc@gmail.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	palmer <palmer@dabbelt.com>, Kito Cheng <kito.cheng@gmail.com>,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Subject: Re: [PATCH] RISC-V: Add autovec FP int->float conversion.
Date: Mon, 26 Jun 2023 15:50:23 -0600	[thread overview]
Message-ID: <2cd3277e-bcb7-5543-f059-74070c5d03f4@gmail.com> (raw)
In-Reply-To: <bc08596b-e2e1-b46c-5697-9e723427ac53@gmail.com>



On 6/26/23 12:58, Robin Dapp wrote:
> Hi,
> 
> this patch adds the autovec expander for vfcvt.f.x.v and tests for it.
> In addition, it modifies the zfhmin-1 test so it doesn't scan for
> "no vectorization" but rather check that we do not emit any (RTL)
> vector operations (other than float/float conversions) with a
> VNx..HFmode.
> 
> Regards
>   Robin
> 
> gcc/ChangeLog:
> 
> 	* config/riscv/autovec.md (<float_cvt><vconvert><mode>2): New
> 	expander.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* gcc.target/riscv/rvv/autovec/conversions/vfcvt_rtz-run.c: Adjust.
> 	* gcc.target/riscv/rvv/autovec/conversions/vfcvt_rtz-rv32gcv.c:
> 	Dito.
> 	* gcc.target/riscv/rvv/autovec/conversions/vfcvt_rtz-rv64gcv.c:
> 	Dito.
> 	* gcc.target/riscv/rvv/autovec/conversions/vfcvt_rtz-template.h:
> 	Dito.
> 	* gcc.target/riscv/rvv/autovec/zvfhmin-1.c: Add int/float conversions.
> 	* gcc.target/riscv/rvv/autovec/conversions/vfcvt-itof-run.c: New test.
> 	* gcc.target/riscv/rvv/autovec/conversions/vfcvt-itof-rv32gcv.c: New test.
> 	* gcc.target/riscv/rvv/autovec/conversions/vfcvt-itof-rv64gcv.c: New test.
> 	* gcc.target/riscv/rvv/autovec/conversions/vfcvt-itof-template.h: New test.
> 	* gcc.target/riscv/rvv/autovec/conversions/vfcvt-itof-zvfh-run.c: New test.
OK.

jeff

  reply	other threads:[~2023-06-26 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 18:58 Robin Dapp
2023-06-26 21:50 ` Jeff Law [this message]
2023-06-26 21:54   ` 钟居哲

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=2cd3277e-bcb7-5543-f059-74070c5d03f4@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=rdapp.gcc@gmail.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).