From: "Li, Pan2" <pan2.li@intel.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Robin Dapp <rdapp.gcc@gmail.com>,
"Wang, Yanzhang" <yanzhang.wang@intel.com>,
kito.cheng <kito.cheng@gmail.com>
Subject: RE: [PATCH v1] RISC-V: Align the predictor style for define_insn_and_split
Date: Thu, 15 Jun 2023 01:07:29 +0000 [thread overview]
Message-ID: <MW5PR11MB590812BC2F79157E091CEBF0A95BA@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <d5a0260c-4a27-1080-9264-e09a6fa2b179@gmail.com>
Committed, thanks Jeff and Juzhe, sorry for misleading.
Pan
-----Original Message-----
From: Jeff Law <jeffreyalaw@gmail.com>
Sent: Thursday, June 15, 2023 2:51 AM
To: juzhe.zhong@rivai.ai; Li, Pan2 <pan2.li@intel.com>; gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Robin Dapp <rdapp.gcc@gmail.com>; Wang, Yanzhang <yanzhang.wang@intel.com>; kito.cheng <kito.cheng@gmail.com>
Subject: Re: [PATCH v1] RISC-V: Align the predictor style for define_insn_and_split
On 6/13/23 20:31, juzhe.zhong@rivai.ai wrote:
> LGTM.
Similarly. If I've interpreted the thread correctly, there aren't any issues created by this patch, though there are some existing issues that need to be addressed independently. The patch itself is definitely the right thing to be doing.
I'd suggest going forward with the commit whenever it's convenient Pan.
Thanks,
Jeff
prev parent reply other threads:[~2023-06-15 1:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 2:15 pan2.li
2023-06-14 2:31 ` juzhe.zhong
2023-06-14 6:00 ` Li, Pan2
2023-06-14 6:09 ` Robin Dapp
2023-06-14 6:30 ` juzhe.zhong
2023-06-14 6:36 ` Li, Pan2
2023-06-14 6:47 ` Robin Dapp
2023-06-14 6:51 ` Li, Pan2
2023-06-14 6:52 ` Robin Dapp
2023-06-14 7:01 ` juzhe.zhong
2023-06-14 7:02 ` Robin Dapp
2023-06-14 7:06 ` Li, Pan2
2023-06-14 18:51 ` Jeff Law
2023-06-15 1:07 ` 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=MW5PR11MB590812BC2F79157E091CEBF0A95BA@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=rdapp.gcc@gmail.com \
--cc=yanzhang.wang@intel.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).