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, 11 Dec 2023 07:56:35 +0000 [thread overview] Message-ID: <bug-112431-4-Zbm8Rt63Qx@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 #15 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:7e854b58084c131fceca9e8fa9dcc7469972e69d commit r14-6400-g7e854b58084c131fceca9e8fa9dcc7469972e69d Author: Juzhe-Zhong <juzhe.zhong@rivai.ai> Date: Sat Dec 9 12:06:29 2023 +0800 RISC-V: Support highest overlap for wv instructions According to RVV ISA, we can allow vwadd.wv v2, v2, v3 overlap. Before this patch: nop vsetivli zero,4,e8,m4,tu,ma vle16.v v8,0(a0) vmv8r.v v0,v8 vwsub.wv v0,v8,v12 nop addi a4,a0,100 vle16.v v8,0(a4) vmv8r.v v24,v8 vwsub.wv v24,v8,v12 nop addi a4,a0,200 vle16.v v8,0(a4) vmv8r.v v16,v8 vwsub.wv v16,v8,v12 nop After this patch: nop vsetivli zero,4,e8,m4,tu,ma vle16.v v0,0(a0) vwsub.wv v0,v0,v4 nop addi a4,a0,100 vle16.v v24,0(a4) vwsub.wv v24,v24,v28 nop addi a4,a0,200 vle16.v v16,0(a4) vwsub.wv v16,v16,v20 PR target/112431 gcc/ChangeLog: * config/riscv/vector.md: Support highest overlap for wv instructions. gcc/testsuite/ChangeLog: * gcc.target/riscv/rvv/base/pr112431-39.c: New test. * gcc.target/riscv/rvv/base/pr112431-40.c: New test. * gcc.target/riscv/rvv/base/pr112431-41.c: New test.
prev parent reply other threads:[~2023-12-11 7:56 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 2023-12-11 7:56 ` cvs-commit at gcc dot gnu.org [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=bug-112431-4-Zbm8Rt63Qx@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).