From: "Li, Pan2" <pan2.li@intel.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
Robin Dapp <rdapp.gcc@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "kito.cheng@gmail.com" <kito.cheng@gmail.com>,
"kito.cheng@sifive.com" <kito.cheng@sifive.com>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"palmer@rivosinc.com" <palmer@rivosinc.com>
Subject: RE: [PATCH] RISC-V: Fix bug of VLA SLP auto-vectorization
Date: Tue, 13 Jun 2023 13:54:43 +0000 [thread overview]
Message-ID: <MW5PR11MB5908424B2519145180A355E9A955A@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <df7bd12d-d50b-4d7c-56f2-86d8b1a3e789@gmail.com>
Committed, thanks Jeff.
Pan
-----Original Message-----
From: Gcc-patches <gcc-patches-bounces+pan2.li=intel.com@gcc.gnu.org> On Behalf Of Jeff Law via Gcc-patches
Sent: Tuesday, June 13, 2023 9:30 PM
To: Robin Dapp <rdapp.gcc@gmail.com>; juzhe.zhong@rivai.ai; gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com; kito.cheng@sifive.com; palmer@dabbelt.com; palmer@rivosinc.com
Subject: Re: [PATCH] RISC-V: Fix bug of VLA SLP auto-vectorization
On 6/13/23 06:16, Robin Dapp wrote:
> Hi Juzhe,
>
> LGTM. You could also add the aarch64 test disclaimer here again, but
> no need for a V2.
Agreed.
jeff
prev parent reply other threads:[~2023-06-13 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 9:30 juzhe.zhong
2023-06-13 12:16 ` Robin Dapp
2023-06-13 13:29 ` Jeff Law
2023-06-13 13:54 ` Li, Pan2 [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=MW5PR11MB5908424B2519145180A355E9A955A@MW5PR11MB5908.namprd11.prod.outlook.com \
--to=pan2.li@intel.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 \
--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).