From: Jeff Law <jeffreyalaw@gmail.com>
To: pan2.li@intel.com, gcc-patches@gcc.gnu.org
Cc: juzhe.zhong@rivai.ai, kito.cheng@gmail.com
Subject: Re: [PATCH v1|GCC-13] RISC-V: Bugfix for riscv-vsetvl pass.
Date: Tue, 18 Jul 2023 07:57:20 -0600 [thread overview]
Message-ID: <3d0b7ae4-454f-dd9e-6cd2-aa09b185a359@gmail.com> (raw)
In-Reply-To: <20230716021622.2831938-1-pan2.li@intel.com>
On 7/15/23 20:16, Pan Li via Gcc-patches wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> This patch comes from part of below change, which locate one bug of rvv
> vsetvel pass when auto-vectorization.
>
> https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624523.html
>
> Unforunately, It is not easy to reproduce this bug by intrinsic APIs
> but it is worth to backport to GCC 13.
>
> Signed-off-by: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc (gen_vsetvl_pat): Add vl parameter.
> (change_vsetvl_insn): Ditto.
> (change_insn): Add validate change as well as assert.
> (pass_vsetvl::backward_demand_fusion): Allow forward.
OK for gcc-13.
jeff
next prev parent reply other threads:[~2023-07-18 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 2:16 pan2.li
2023-07-18 13:57 ` Jeff Law [this message]
2023-07-18 14:06 ` Li, Pan2
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=3d0b7ae4-454f-dd9e-6cd2-aa09b185a359@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=pan2.li@intel.com \
/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).