public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112431] RISC-V GCC-15 feature: Support register overlap on widen RVV instructions Date: Mon, 04 Dec 2023 13:48:04 +0000 [thread overview] Message-ID: <bug-112431-4-WtikUxbJ6O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112431-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112431 --- Comment #14 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Pan Li <panli@gcc.gnu.org>: https://gcc.gnu.org/g:018ba3ac952bed4ae01344c060360f13f7cc084a commit r14-6118-g018ba3ac952bed4ae01344c060360f13f7cc084a Author: Juzhe-Zhong <juzhe.zhong@rivai.ai> Date: Mon Dec 4 21:44:56 2023 +0800 RISC-V: Fix overlap group incorrect overlap on v0 In serious high register pressure case (appended in this patch): We see vluxei8.v v0,(s1),v1,v0.t which is not allowed. Since according to RVV ISA: +;; The destination vector register group for a masked vector instruction cannot overlap the source mask register (v0), +;; unless the destination vector register is being written with a mask value (e.g., compares) or the scalar result of a reduction. Such case doesn't have spillings, however, we expect such case should be spilled and reload data. The rootcause is I made a mistake in previous patch on matching dest operand and mask operand constraints: dest: "=vr" mask: "vmWc1" After this patch: dest: "vd,vr" mask: "vm,Wc1" make EEW widening pattern are same as other instruction patterns. PR target/112431 gcc/ChangeLog: * config/riscv/vector.md: Fix incorrect overlap in v0. gcc/testsuite/ChangeLog: * gcc.target/riscv/rvv/base/pr112431-34.c: New test.
next prev parent reply other threads:[~2023-12-04 13:48 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-08 0:15 [Bug c/112431] New: " juzhe.zhong at rivai dot ai 2023-11-08 0:16 ` [Bug c/112431] " juzhe.zhong at rivai dot ai 2023-11-08 0:16 ` juzhe.zhong at rivai dot ai 2023-11-08 1:56 ` kito at gcc dot gnu.org 2023-11-12 21:18 ` pinskia at gcc dot gnu.org 2023-11-29 9:37 ` [Bug target/112431] " cvs-commit at gcc dot gnu.org 2023-11-30 1:16 ` cvs-commit at gcc dot gnu.org 2023-11-30 2:40 ` cvs-commit at gcc dot gnu.org 2023-11-30 10:50 ` cvs-commit at gcc dot gnu.org 2023-11-30 12:11 ` cvs-commit at gcc dot gnu.org 2023-12-01 12:09 ` cvs-commit at gcc dot gnu.org 2023-12-01 12:09 ` cvs-commit at gcc dot gnu.org 2023-12-04 10:45 ` cvs-commit at gcc dot gnu.org 2023-12-04 11:21 ` juzhe.zhong at rivai dot ai 2023-12-04 13:36 ` cvs-commit at gcc dot gnu.org 2023-12-04 13:48 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-11 7:56 ` cvs-commit at gcc dot gnu.org
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=bug-112431-4-WtikUxbJ6O@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).