From: Robin Dapp <rdapp.gcc@gmail.com>
To: Juzhe-Zhong <juzhe.zhong@rivai.ai>, gcc-patches@gcc.gnu.org
Cc: rdapp.gcc@gmail.com, kito.cheng@gmail.com, kito.cheng@sifive.com,
palmer@dabbelt.com, palmer@rivosinc.com, jeffreyalaw@gmail.com
Subject: Re: [PATCH V4] RISC-V: Support gather_load/scatter RVV auto-vectorization
Date: Fri, 7 Jul 2023 14:34:06 +0200 [thread overview]
Message-ID: <217c769f-d97c-e381-1b66-542b563db12b@gmail.com> (raw)
In-Reply-To: <20230707104847.271195-1-juzhe.zhong@rivai.ai>
Hi Juzhe,
thanks, the somewhat unified modulo is IMHO a more readable.
Could probably still be improved but OK with me for now.
> + if (is_dummy_len)
> + {
> + rtx dummy_len = gen_reg_rtx (Pmode);
Can we call this is_vlmax_len/is_vlmax and vlmax_len or so?
> + if (inner_offsize < inner_vsize)
> + {
> + /* 7.2. Vector Load/Store Addressing Modes.
> + If the vector offset elements are narrower than XLEN, they are
> + zero-extended to XLEN before adding to the ptr effective address. If
> + the vector offset elements are wider than XLEN, the least-significant
> + XLEN bits are used in the address calculation. An implementation must
> + raise an illegal instruction exception if the EEW is not supported for
> + offset elements. */
> + if (!zero_extend_p || (zero_extend_p && scale_log2 != 0))
Hehe I really thought we have a widening shift, well ;)
I see, the zero extension refers to this part of the GCC docs
"multiply the extended offset by operand 4;"
and not to the RVV spec. You could clarify this then, saying
that the RVV spec only refers to the scale_log == 0 case.
The rest LGTM now, no separate revision needed for those nits.
Regards
Robin
next prev parent reply other threads:[~2023-07-07 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 10:48 Juzhe-Zhong
2023-07-07 12:34 ` Robin Dapp [this message]
2023-07-07 14:34 ` 钟居哲
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=217c769f-d97c-e381-1b66-542b563db12b@gmail.com \
--to=rdapp.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.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).