public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114109] x264 satd vectorization vs LLVM
Date: Mon, 26 Feb 2024 11:24:55 +0000 [thread overview]
Message-ID: <bug-114109-4-2kBh2rd5gS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114109-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114109
--- Comment #3 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
(In reply to Robin Dapp from comment #2)
> It is vectorized with a higher zvl, e.g. zvl512b, refer
> https://godbolt.org/z/vbfjYn5Kd.
OK. I see. But Clang generates many slide instruction which are expensive in
real hardware.
And also vluxei64 is also expensive.
I am not sure which is better. It should be tested on real RISC-V hardware to
evaluate their performance rather than simply tested on SPIKE/QEMU dynamic
instructions count.
next prev parent reply other threads:[~2024-02-26 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 10:28 [Bug middle-end/114109] New: " rdapp at gcc dot gnu.org
2024-02-26 10:44 ` [Bug middle-end/114109] " juzhe.zhong at rivai dot ai
2024-02-26 11:20 ` rdapp at gcc dot gnu.org
2024-02-26 11:24 ` juzhe.zhong at rivai dot ai [this message]
2024-02-26 11:26 ` rdapp at gcc dot gnu.org
2024-02-26 15:08 ` rguenth at gcc dot gnu.org
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=bug-114109-4-2kBh2rd5gS@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).