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 target/112092] RISC-V: Wrong RVV code produced for vsetvl-11.c and vsetvlmax-8.c
Date: Thu, 26 Oct 2023 07:08:16 +0000 [thread overview]
Message-ID: <bug-112092-4-hbG6dZsMWC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112092-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112092
--- Comment #6 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
> I have troubles chasing one down and the source code is so
> convoluted with macros I can't even find the implementation.
I am sorry for causing confusion to you here.
But because of the RVV fusion rules are so complicated, we define it in
riscv-vsetvl.def. To understand the codes, I suggest you directly read the
riscv-vsetvl.def
We define all compatible, fusion, available rules there.
For example, vle16.v (e16, m1 ) is compatible with vadd.vv (e32, mf2 ),
In this case, adjacent 2 instructions "vle16" (e16m1) and vadd.vv (e32mf2) can
have the same vsetvl (vsetvl e32mf2).
Wheras vsub.vv(e16,m1) and vadd (e32 mf2), they are not compatible.
next prev parent reply other threads:[~2023-10-26 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 1:00 [Bug target/112092] New: " macro at orcam dot me.uk
2023-10-26 1:46 ` [Bug target/112092] " juzhe.zhong at rivai dot ai
2023-10-26 1:57 ` juzhe.zhong at rivai dot ai
2023-10-26 4:01 ` macro at orcam dot me.uk
2023-10-26 6:38 ` kito at gcc dot gnu.org
2023-10-26 6:51 ` juzhe.zhong at rivai dot ai
2023-10-26 7:08 ` juzhe.zhong at rivai dot ai [this message]
2023-10-26 23:31 ` macro at orcam dot me.uk
2023-10-27 0:57 ` juzhe.zhong at rivai dot ai
2023-10-27 1:03 ` juzhe.zhong at rivai dot ai
2023-10-31 13:58 ` [Bug target/112092] RISC-V: Suboptimal " macro at orcam dot me.uk
2023-11-08 6:38 ` cvs-commit at gcc dot gnu.org
2023-11-08 6:39 ` juzhe.zhong at rivai dot ai
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-112092-4-hbG6dZsMWC@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).