From: "Li, Pan2" <pan2.li@intel.com>
To: "Jeff Law" <jeffreyalaw@gmail.com>, 钟居哲 <juzhe.zhong@rivai.ai>,
丁乐华 <lehua.ding@rivai.ai>, gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "Wang, Yanzhang" <yanzhang.wang@intel.com>,
kito.cheng <kito.cheng@gmail.com>, palmer <palmer@rivosinc.com>,
rdapp.gcc <rdapp.gcc@gmail.com>
Subject: RE: [PATCH] RISC-V: Add tuple vector mode psABI checking and simplify code
Date: Tue, 20 Jun 2023 01:16:09 +0000 [thread overview]
Message-ID: <MW5PR11MB5908A2361C734FA4AE5E02D8A95CA@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <e165d06e-6c83-a0f3-e7da-15b535122e2f@gmail.com>
Committed, thanks Jeff.
-----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 20, 2023 2:04 AM
To: 钟居哲 <juzhe.zhong@rivai.ai>; 丁乐华 <lehua.ding@rivai.ai>; gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Wang, Yanzhang <yanzhang.wang@intel.com>; kito.cheng <kito.cheng@gmail.com>; palmer <palmer@rivosinc.com>; rdapp.gcc <rdapp.gcc@gmail.com>
Subject: Re: [PATCH] RISC-V: Add tuple vector mode psABI checking and simplify code
On 6/18/23 07:16, 钟居哲 wrote:
> Thanks for cleaning up codes for future's ABI support patch.
> Let's wait for Jeff or Robin comments.
Looks reasonable to me given the state we're in WRT psabi and vectors.
jeff
next prev parent reply other threads:[~2023-06-20 1:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 11:41 Lehua Ding
2023-06-18 13:16 ` 钟居哲
2023-06-19 18:03 ` Jeff Law
2023-06-20 1:16 ` Li, Pan2 [this message]
2023-06-20 12:10 ` Robin Dapp
2023-06-20 12:58 ` Lehua Ding
2023-06-20 13:01 ` Robin Dapp
2023-06-20 13:13 ` Lehua Ding
2023-06-20 13:44 ` Lehua Ding
2023-06-20 13:50 ` Robin Dapp
2023-06-20 14:03 ` Robin Dapp
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=MW5PR11MB5908A2361C734FA4AE5E02D8A95CA@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=lehua.ding@rivai.ai \
--cc=palmer@rivosinc.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).