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/112599] RISC-V regression testsuite errors with rv64gcv_zvl1024b Date: Fri, 24 Nov 2023 06:34:19 +0000 [thread overview] Message-ID: <bug-112599-4-veO11aQCBF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112599-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112599 --- Comment #4 from CVS 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:d83013b88b74d1f1f774d94ca950d3b6dba26e5d commit r14-5812-gd83013b88b74d1f1f774d94ca950d3b6dba26e5d Author: Juzhe-Zhong <juzhe.zhong@rivai.ai> Date: Fri Nov 24 07:18:00 2023 +0800 RISC-V: Optimize a special case of VLA SLP When working on fixing bugs of zvl1024b. I notice a special VLA SLP case can be better optimized. v = vec_perm (op1, op2, { nunits - 1, nunits, nunits + 1, ... }) Before this patch, we are using genriec approach (vrgather): vid vadd.vx vrgather vmsgeu vrgather With this patch, we use vec_extract + slide1up: scalar = vec_extract (last element of op1) v = slide1up (op2, scalar) Tested on zvl128b/zvl256b/zvl512b/zvl1024b of both RV32 and RV64 no regression. Ok for trunk ? PR target/112599 gcc/ChangeLog: * config/riscv/riscv-v.cc (shuffle_extract_and_slide1up_patterns): New function. (expand_vec_perm_const_1): Add new optimization. gcc/testsuite/ChangeLog: * gcc.target/riscv/rvv/autovec/pr112599-2.c: New test.
next prev parent reply other threads:[~2023-11-24 6:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-17 21:19 [Bug target/112599] New: " patrick at rivosinc dot com 2023-11-17 21:21 ` [Bug target/112599] " patrick at rivosinc dot com 2023-11-21 17:47 ` patrick at rivosinc dot com 2023-11-23 12:09 ` cvs-commit at gcc dot gnu.org 2023-11-24 6:34 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-26 9:15 ` cvs-commit at gcc dot gnu.org 2023-11-27 17:57 ` patrick at rivosinc dot com 2023-12-04 21:41 ` patrick at rivosinc dot com 2023-12-11 23:59 ` patrick at rivosinc dot com 2024-01-24 23:53 ` patrick at rivosinc dot com
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-112599-4-veO11aQCBF@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).