From: Jeff Law <jeffreyalaw@gmail.com>
To: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, palmer@dabbelt.com
Subject: Re: [PATCH] RISC-V: Fix SEW64 of vrsub.vx runtime fail in RV32 system
Date: Wed, 5 Apr 2023 07:49:04 -0600 [thread overview]
Message-ID: <27be39e6-3cbb-bd80-a058-652bf1f773fb@gmail.com> (raw)
In-Reply-To: <20230403003855.113601-1-juzhe.zhong@rivai.ai>
On 4/2/23 18:38, juzhe.zhong@rivai.ai wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> It's quite obvious that the order of vrsub SEW64 is wrong.
>
> gcc/ChangeLog:
>
> * config/riscv/vector.md: Fix incorrect operand order.
>
> gcc/testsuite/ChangeLog:
>
> * g++.target/riscv/rvv/base/bug-23.C: New test.
Thanks. Installed.
Note I still think we need to fix the formatting issues, but that's a
larger change that we can tackle independently of the bugfix.
jeff
prev parent reply other threads:[~2023-04-05 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 0:38 juzhe.zhong
2023-04-03 4:13 ` Jeff Law
2023-04-03 4:18 ` juzhe.zhong
2023-04-05 1:34 ` Jeff Law
2023-04-05 13:49 ` Jeff Law [this message]
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=27be39e6-3cbb-bd80-a058-652bf1f773fb@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).