From: Jeff Law <jeffreyalaw@gmail.com>
To: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, palmer@dabbelt.com
Subject: Re: [PATCH] RISC-V: Remove unit-stride store from ta attribute
Date: Fri, 16 Dec 2022 13:01:04 -0700 [thread overview]
Message-ID: <d3713478-01ac-6cd5-81f0-1887daef87ca@gmail.com> (raw)
In-Reply-To: <20221214113641.63320-1-juzhe.zhong@rivai.ai>
On 12/14/22 04:36, juzhe.zhong@rivai.ai wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> Since store instructions doesn't care about tail policy, we remove
> vste from "ta" attribute. Hence, we could have more fusion chances
> and better optimization.
>
> gcc/ChangeLog:
>
> * config/riscv/vector.md: Remove vste.
Just to confirm that I understand the basic model. Vector stores only
update active elements, thus they don't care about tail policy, right?
Assuming that's the case, then this is OK.
jeff
next prev parent reply other threads:[~2022-12-16 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 11:36 juzhe.zhong
2022-12-16 20:01 ` Jeff Law [this message]
2022-12-16 21:59 ` Palmer Dabbelt
2022-12-16 23:00 ` Andrew Waterman
2022-12-17 1:22 ` 钟居哲
2022-12-19 15:06 ` Kito Cheng
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=d3713478-01ac-6cd5-81f0-1887daef87ca@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).