From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>, juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org, kito-cheng <kito.cheng@sifive.com>
Subject: Re: [PATCH] RISC-V: Fix bugs of ternary integer and floating-point ternary intrinsics.
Date: Tue, 14 Mar 2023 08:50:55 -0600 [thread overview]
Message-ID: <538e4a8e-f5f1-d625-c589-5e679884e864@gmail.com> (raw)
In-Reply-To: <CA+yXCZB5cwKHEYxEoXPn1d_St2RnCBpwV6FCPB5=CX5PmHP_FQ@mail.gmail.com>
On 3/13/23 20:37, Kito Cheng via Gcc-patches wrote:
> IIRC the canonical form of (plus (op) (mult (op) (op))) is (plus
> (mult (op) (op) (op)), so using the first form might not friendly for
> the combine pass.
You're correct. The other form shouldn't be used at all and should not
appear in the MD files.
jeff
next prev parent reply other threads:[~2023-03-14 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 2:23 juzhe.zhong
2023-03-14 2:37 ` Kito Cheng
2023-03-14 14:50 ` Jeff Law [this message]
2023-03-15 5:23 juzhe.zhong
2023-03-15 6:37 juzhe.zhong
2023-03-19 17:03 ` Jeff Law
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=538e4a8e-f5f1-d625-c589-5e679884e864@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.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).