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/112855] [14] RISC-V vector: vsetivli clobbers variable value
Date: Wed, 06 Dec 2023 14:36:09 +0000	[thread overview]
Message-ID: <bug-112855-4-rFgXmdJhFE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112855-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:c9d5b46a25547035e381b0246de5cb553ca8b02d

commit r14-6222-gc9d5b46a25547035e381b0246de5cb553ca8b02d
Author: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Date:   Wed Dec 6 22:26:46 2023 +0800

    RISC-V: Fix VSETVL PASS bug

    As PR112855 mentioned, the VSETVL PASS insert vsetvli in unexpected
location.

    Due to 2 reasons:
    1. incorrect transparant computation LCM data. We need to check VL operand
defs and uses.
    2. incorrect fusion of unrelated edge which is the edge never reach the
vsetvl expression.

            PR target/112855

    gcc/ChangeLog:

            * config/riscv/riscv-vsetvl.cc
            (pre_vsetvl::compute_lcm_local_properties): Fix transparant LCM
data.
            (pre_vsetvl::earliest_fuse_vsetvl_info): Disable earliest fusion
for unrelated edge.

    gcc/testsuite/ChangeLog:

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

  parent reply	other threads:[~2023-12-06 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05  5:21 [Bug target/112855] New: [14] RISC-V vector: overwriting stack args patrick at rivosinc dot com
2023-12-05 18:54 ` [Bug target/112855] [14] RISC-V vector: vsetivli clobbers variable value patrick at rivosinc dot com
2023-12-06 14:36 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-06 18:54 ` 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-112855-4-rFgXmdJhFE@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).