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 11:15:22 -0700 (PDT) [thread overview]
Message-ID: <mhng-4dc3b20e-d17a-4374-8956-172950614d65@palmer-ri-x1c9a> (raw)
In-Reply-To: <89831580-fc21-f769-2f50-fffe57e8afe1@gmail.com>
On Sat, 29 Apr 2023 10:52:50 PDT (-0700), jeffreyalaw@gmail.com wrote:
>
>
> On 4/29/23 11:48, Palmer Dabbelt wrote:
>
>>> 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.
> Well, when a user mode SPEC run goes from ~15 minutes to multiple hours
> for a single input workload within specint it becomes a development
> problem. Daniel is loosely affiliated with my group in Ventana, so I
> can bug him with this kind of stuff.
We've got another team actually doing the mechanics of the SPEC runs, we
just do the compiler. So while I guess it is a problem, it's not my
problem ;)
Maybe not the best way to go about things, but there's only so much that
can be done...
next prev parent reply other threads:[~2023-04-29 18:15 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
2023-04-29 17:52 ` Jeff Law
2023-04-29 18:15 ` Palmer Dabbelt [this message]
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-4dc3b20e-d17a-4374-8956-172950614d65@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).