From: Richard Biener <rguenther@suse.de>
To: Robin Dapp <rdapp.gcc@gmail.com>
Cc: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [PATCH] VECT: Support floating-point in-order reduction for length loop control
Date: Thu, 20 Jul 2023 07:21:15 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2307200720590.12935@jbgna.fhfr.qr> (raw)
In-Reply-To: <94edbd35-4e11-15f3-62ef-af492ac2189e@gmail.com>
On Thu, 20 Jul 2023, Robin Dapp wrote:
> Hi Juzhe,
>
> I just noticed that we recently started calling things MASK_LEN
> (instead of LEN_MASK before) with the reductions. Wouldn't we want
> to be consistent here? Especially as the length takes precedence.
> I realize the preparational work like optabs is already upstream
> but still wanted to bring it up.
Didn't notice that but yes, consistency would be nice to have.
Richard.
next prev parent reply other threads:[~2023-07-20 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 6:07 juzhe.zhong
2023-07-20 6:22 ` Robin Dapp
2023-07-20 6:33 ` juzhe.zhong
2023-07-20 7:21 ` Richard Biener [this message]
2023-07-20 7:26 ` juzhe.zhong
2023-07-21 10:08 ` juzhe.zhong
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=nycvar.YFH.7.77.849.2307200720590.12935@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=rdapp.gcc@gmail.com \
--cc=richard.sandiford@arm.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).