From: Palmer Dabbelt <palmer@dabbelt.com>
To: jeffreyalaw@gmail.com
Cc: gcc-patches@gcc.gnu.org, pan2.li@intel.com,
yanzhang.wang@intel.com, juzhe.zhong@rivai.ai,
kito.cheng@sifive.com
Subject: Re: [PATCH] RISC-V: Allow RVV VMS{Compare}(V1, V1) simplify to VMSET
Date: Sat, 29 Apr 2023 10:48:20 -0700 (PDT) [thread overview]
Message-ID: <mhng-4a07f7f0-e84b-44f4-a62e-7d6c286f9a02@palmer-ri-x1c9a> (raw)
In-Reply-To: <ae8b67dc-5774-25d3-2a20-8a1aecc91e05@gmail.com>
On Sat, 29 Apr 2023 10:46:37 PDT (-0700), jeffreyalaw@gmail.com wrote:
>
>
> On 4/29/23 11:28, Palmer Dabbelt wrote:
>> On Sat, 29 Apr 2023 10:21:53 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
>>> On Sat, Apr 29, 2023 at 8:06 AM Jeff Law via Gcc-patches <
>>> gcc-patches@gcc.gnu.org> wrote:
>>>>
>>>>
>>>>
>>>> On 4/28/23 20:55, Li, Pan2 wrote:
>>>> > Thanks Jeff for comments.
>>>> >
>>>> > It makes sense to me. For the EQ operator we should have CONSTM1.
>>>> That's not the way I interpret the RVV documentation. Of course it's
>>>> not terribly clear. I guess one could do some experiments with qemu
>>>> or try to dig into the sail code and figure out the intent from those.
>>
>> QEMU specifically takes advantage of the behavior Andrew is pointing out
>> it the spec, and will soon do so more aggressively (assuming the patches
>> Daniel just sent out get merged).
> Yea. And taking advantage of that behavior is definitely a performance
> issue for QEMU. There's still work to do though. QEMU on vector code
> is running crazy slow.
I guess we're kind of off the rails for a GCC patch, but that's
definately true. Across the board RVV is going to just need a lot of
work, it's very different than SVE or AVX.
Unfortunately QEMU performance isn't really a priority on our end, but
it's great to see folks digging into it.
next prev parent reply other threads:[~2023-04-29 17:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 15:21 pan2.li
2023-04-28 21:47 ` Jeff Law
2023-04-29 2:55 ` Li, Pan2
2023-04-29 13:35 ` Li, Pan2
2023-04-29 15:05 ` Jeff Law
2023-04-29 17:21 ` Andrew Waterman
2023-04-29 17:28 ` Palmer Dabbelt
2023-04-29 17:46 ` Jeff Law
2023-04-29 17:48 ` Palmer Dabbelt [this message]
2023-04-29 17:52 ` Jeff Law
2023-04-29 18:15 ` Palmer Dabbelt
2023-04-29 17:49 ` Jeff Law
2023-04-30 1:40 ` Kito Cheng
2023-04-30 14:21 ` Li, Pan2
2023-05-02 16:28 ` Jeff Law
2023-05-03 11:17 ` Li, Pan2
2023-05-05 12:30 ` Li, Pan2
2023-05-05 12:37 ` Kito Cheng
2023-05-05 12:45 ` Li, Pan2
2023-05-05 14:51 ` Kito Cheng
2023-04-29 13:32 ` [PATCH v2] " pan2.li
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=mhng-4a07f7f0-e84b-44f4-a62e-7d6c286f9a02@palmer-ri-x1c9a \
--to=palmer@dabbelt.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.com \
--cc=pan2.li@intel.com \
--cc=yanzhang.wang@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).