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/113697] RISC-V: Redundant vsetvl insn in function
Date: Fri, 02 Feb 2024 17:37:03 +0000	[thread overview]
Message-ID: <bug-113697-4-P1sWTnzFI8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113697-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113697

--- Comment #1 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:922e4599e6261644d336b009b6901cd221ec95fd

commit r14-8757-g922e4599e6261644d336b009b6901cd221ec95fd
Author: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Date:   Fri Feb 2 09:56:59 2024 +0800

    RISC-V: Expand VLMAX scalar move in reduction

    This patch fixes the following:

            vsetvli a5,a1,e32,m1,tu,ma
            slli    a4,a5,2
            sub     a1,a1,a5
            vle32.v v2,0(a0)
            add     a0,a0,a4
            vadd.vv v1,v2,v1
            bne     a1,zero,.L3
            vsetivli        zero,1,e32,m1,ta,ma
            vmv.s.x v2,zero
            vsetvli a5,zero,e32,m1,ta,ma              ---> Redundant vsetvl.
            vredsum.vs      v1,v1,v2
            vmv.x.s a0,v1
            ret

    VSETVL PASS is able to fuse avl = 1 of scalar move and VLMAX avl of
reduction.

    However, this following RTL blocks the fusion in dependence analysis in
VSETVL PASS:

    (insn 49 24 50 5 (set (reg:RVVM1SI 98 v2 [148])
            (if_then_else:RVVM1SI (unspec:RVVMF32BI [
                        (const_vector:RVVMF32BI [
                                (const_int 1 [0x1])
                                repeat [
                                    (const_int 0 [0])
                                ]
                            ])
                        (const_int 1 [0x1])
                        (const_int 2 [0x2]) repeated x2
                        (const_int 0 [0])
                        (reg:SI 66 vl)
                        (reg:SI 67 vtype)
                    ] UNSPEC_VPREDICATE)
                (const_vector:RVVM1SI repeat [
                        (const_int 0 [0])
                    ])
                (unspec:RVVM1SI [
                        (reg:DI 0 zero)
                    ] UNSPEC_VUNDEF))) 3813 {*pred_broadcastrvvm1si_zero}
         (nil))
    (insn 50 49 51 5 (set (reg:DI 15 a5 [151])                          ----> 
It set a5, blocks the following VLMAX into the scalar move above.
            (unspec:DI [
                    (const_int 32 [0x20])
                ] UNSPEC_VLMAX)) 2566 {vlmax_avldi}
         (expr_list:REG_EQUIV (unspec:DI [
                    (const_int 32 [0x20])
                ] UNSPEC_VLMAX)
            (nil)))
    (insn 51 50 52 5 (set (reg:RVVM1SI 97 v1 [150])
            (unspec:RVVM1SI [
                    (unspec:RVVMF32BI [
                            (const_vector:RVVMF32BI repeat [
                                    (const_int 1 [0x1])
                                ])
                            (reg:DI 15 a5 [151])
                            (const_int 2 [0x2])
                            (const_int 1 [0x1])
                            (reg:SI 66 vl)
                            (reg:SI 67 vtype)
                        ] UNSPEC_VPREDICATE)
                    (unspec:RVVM1SI [
                            (reg:RVVM1SI 97 v1 [orig:134 vect_result_14.6 ]
[134])
                            (reg:RVVM1SI 98 v2 [148])
                        ] UNSPEC_REDUC_SUM)
                    (unspec:RVVM1SI [
                            (reg:DI 0 zero)
                        ] UNSPEC_VUNDEF)
                ] UNSPEC_REDUC)) 17541 {pred_redsumrvvm1si}
         (expr_list:REG_DEAD (reg:RVVM1SI 98 v2 [148])
            (expr_list:REG_DEAD (reg:SI 66 vl)
                (expr_list:REG_DEAD (reg:DI 15 a5 [151])
                    (expr_list:REG_DEAD (reg:DI 0 zero)
                        (nil))))))

    Such situation can only happen on auto-vectorization, never happen on
intrinsic codes.
    Since the reduction is passed VLMAX AVL, it should be more natural to pass
VLMAX to the scalar move which initial the value of the reduction.

    After this patch:

            vsetvli a5,a1,e32,m1,tu,ma
            slli    a4,a5,2
            sub     a1,a1,a5
            vle32.v v2,0(a0)
            add     a0,a0,a4
            vadd.vv v1,v2,v1
            bne     a1,zero,.L3
            vsetvli a5,zero,e32,m1,ta,ma
            vmv.s.x v2,zero
            vredsum.vs      v1,v1,v2
            vmv.x.s a0,v1
            ret

    Tested on both RV32/RV64 no regression.

            PR target/113697

    gcc/ChangeLog:

            * config/riscv/riscv-v.cc (expand_reduction): Pass VLMAX avl to
scalar move.

    gcc/testsuite/ChangeLog:

            * gcc.target/riscv/rvv/autovec/pr113697.c: New test.

  reply	other threads:[~2024-02-02 17:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  1:59 [Bug c/113697] New: " pan2.li at intel dot com
2024-02-02 17:37 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-04  0:46 ` [Bug target/113697] " pan2.li at intel 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-113697-4-P1sWTnzFI8@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: 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).