From: Jeff Law <jeffreyalaw@gmail.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "kito.cheng" <kito.cheng@gmail.com>,
"Kito.cheng" <kito.cheng@sifive.com>,
Robin Dapp <rdapp.gcc@gmail.com>
Subject: Re: [PATCH] RISC-V: Expand VLMAX scalar move in reduction
Date: Mon, 5 Feb 2024 08:34:06 -0700 [thread overview]
Message-ID: <5ba23b66-6338-4e2e-bc48-a5f3ff5fbbfa@gmail.com> (raw)
In-Reply-To: <5B8117E9C28EBC42+202402051437529412972@rivai.ai>
On 2/4/24 23:37, juzhe.zhong@rivai.ai wrote:
> I think it just trigger a latent bug that we didn't encounter.
>
> Hi, Robin. Would you mind give me preprocessed file to reproduce the issue ?
>
> I suspect it triggers latent bug in VSETVL PASS.
I've got a few minutes this morning before meetings start. I'm going to
try and trigger this with LTO off, which would help dramatically with
our ability to provide a testcase.
jeff
next prev parent reply other threads:[~2024-02-05 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 1:56 Juzhe-Zhong
2024-02-02 9:50 ` Kito Cheng
2024-02-05 3:26 ` Jeff Law
2024-02-05 4:36 ` Jeff Law
2024-02-05 6:37 ` juzhe.zhong
2024-02-05 15:34 ` Jeff Law [this message]
2024-02-05 19:09 ` Jeff Law
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=5ba23b66-6338-4e2e-bc48-a5f3ff5fbbfa@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=rdapp.gcc@gmail.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).