public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Lehua Ding" <lehua.ding@rivai.ai>
To: 钟居哲 <juzhe.zhong@rivai.ai>, "kito.cheng" <kito.cheng@gmail.com>,
	"Robin Dapp" <rdapp.gcc@gmail.com>
Cc: "Jeff Law" <jeffreyalaw@gmail.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	"Kito Cheng" <kito.cheng@sifive.com>, palmer <palmer@dabbelt.com>,
	palmer <palmer@rivosinc.com>
Subject: Re:  [PATCH] RISC-V: Support vfwnmacc/vfwmsac/vfwnmsac combine lowering
Date: Mon, 3 Jul 2023 17:27:48 +0800	[thread overview]
Message-ID: <tencent_0823558666B7A71651373184@qq.com> (raw)
In-Reply-To: <70CF4A581CAB6B04+202307031712062144808@rivai.ai>

[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]

Commited, thanks Robin, Kito, and Jeff.
&nbsp;
&nbsp;
------------------&nbsp;Original&nbsp;------------------
From: &nbsp;"juzhe.zhong@rivai.ai"<juzhe.zhong@rivai.ai&gt;;
Date: &nbsp;Mon, Jul 3, 2023 05:12 PM
To: &nbsp;"kito.cheng"<kito.cheng@gmail.com&gt;; "Robin Dapp"<rdapp.gcc@gmail.com&gt;; 
Cc: &nbsp;"Jeff Law"<jeffreyalaw@gmail.com&gt;; "gcc-patches"<gcc-patches@gcc.gnu.org&gt;; "Kito Cheng"<kito.cheng@sifive.com&gt;; "palmer"<palmer@dabbelt.com&gt;; "palmer"<palmer@rivosinc.com&gt;; "丁乐华"<lehua.ding@rivai.ai&gt;; 
Subject: &nbsp;Re: Re: [PATCH] RISC-V: Support vfwnmacc/vfwmsac/vfwnmsac combine lowering

&nbsp;

 Thanks kito. 
Lehua will merge it for me.
 


 juzhe.zhong@rivai.ai


 &nbsp;
From:&nbsp;Kito Cheng
Date:&nbsp;2023-07-03 17:01
To:&nbsp;Robin Dapp
CC:&nbsp;juzhe.zhong@rivai.ai; jeffreyalaw; gcc-patches; Kito.cheng; palmer; palmer
Subject:&nbsp;Re: [PATCH] RISC-V: Support vfwnmacc/vfwmsac/vfwnmsac combine lowering


Tried on local, widen-complicate-7.c, widen-complicate-8.c and
 widen-complicate-9.c need those bridge pattern, otherwise will fail to
 combine, so give an explicitly LGTM from my side.
 &nbsp;
 On Mon, Jul 3, 2023 at 3:48 PM Robin Dapp via Gcc-patches
 <gcc-patches@gcc.gnu.org&gt; wrote:
 &gt;
 &gt; To reiterate, this is OK from my side.&nbsp; As discussed in the other
 &gt; thread, Jeff would like to have more info on whether a bridge pattern
 &gt; is needed at all and I agreed to get back to it in a while.&nbsp; Until
 &gt; then, we can merge this.
 &gt;
 &gt; Regards
 &gt;&nbsp; Robin
 &gt;
 &nbsp;

      reply	other threads:[~2023-07-03  9:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 11:55 Juzhe-Zhong
2023-06-28 18:16 ` Jeff Law
2023-06-28 22:10   ` 钟居哲
2023-06-28 22:43     ` Jeff Law
2023-06-28 22:56       ` 钟居哲
2023-06-29 23:43         ` Jeff Law
2023-06-30  1:14           ` juzhe.zhong
2023-06-30  1:26             ` Jeff Law
2023-06-30  1:32               ` juzhe.zhong
2023-07-03  7:48                 ` Robin Dapp
2023-07-03  9:01                   ` Kito Cheng
2023-07-03  9:12                     ` juzhe.zhong
2023-07-03  9:27                       ` Lehua Ding [this message]

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=tencent_0823558666B7A71651373184@qq.com \
    --to=lehua.ding@rivai.ai \
    --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 \
    --cc=rdapp.gcc@gmail.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).