From: "Li, Pan2" <pan2.li@intel.com>
To: juzhe.zhong <juzhe.zhong@rivai.ai>,
"Wang, Yanzhang" <yanzhang.wang@intel.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"kito.cheng@sifive.com" <kito.cheng@sifive.com>,
"Wang, Yanzhang" <yanzhang.wang@intel.com>
Subject: RE: [PATCH] RISC-V: ICE for vlmul_ext_v intrinsic API
Date: Wed, 26 Apr 2023 12:22:51 +0000 [thread overview]
Message-ID: <SJ0PR11MB5919AB656AF2409335D67F6DA9659@SJ0PR11MB5919.namprd11.prod.outlook.com> (raw)
In-Reply-To: <C0EDB34B44515F0E+7C4404C2-68B6-40DA-B9F4-D633858D487C@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
Great! Thanks yanzhang.
Could you please help to add some text about the changes below? Or kito may meet some error by git hook when commit the PATCH.
gcc/ChangeLog:
* config/riscv/vector-iterators.md: <- add text for change.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/base/vlmul_ext-1.c: New test.
Pan
From: juzhe.zhong <juzhe.zhong@rivai.ai>
Sent: Wednesday, April 26, 2023 8:15 PM
To: Wang, Yanzhang <yanzhang.wang@intel.com>
Cc: gcc-patches@gcc.gnu.org; kito.cheng@sifive.com; Li, Pan2 <pan2.li@intel.com>; Wang, Yanzhang <yanzhang.wang@intel.com>
Subject: Re: [PATCH] RISC-V: ICE for vlmul_ext_v intrinsic API
LGTM. Thanks for fixing my silly mistake.
---- Replied Message ----
From
yanzhang.wang@intel.com<yanzhang.wang@intel.com><mailto:yanzhang.wang@intel.com>
Date
04/26/2023 20:05
To
gcc-patches@gcc.gnu.org<gcc-patches@gcc.gnu.org><mailto:gcc-patches@gcc.gnu.org>
Cc
juzhe.zhong@rivai.ai<juzhe.zhong@rivai.ai><mailto:juzhe.zhong@rivai.ai>,
kito.cheng@sifive.com<kito.cheng@sifive.com><mailto:kito.cheng@sifive.com>,
pan2.li@intel.com<pan2.li@intel.com><mailto:pan2.li@intel.com>,
yanzhang.wang@intel.com<yanzhang.wang@intel.com><mailto:yanzhang.wang@intel.com>
Subject
[PATCH] RISC-V: ICE for vlmul_ext_v intrinsic API
next prev parent reply other threads:[~2023-04-26 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 12:05 yanzhang.wang
[not found] ` <C0EDB34B44515F0E+7C4404C2-68B6-40DA-B9F4-D633858D487C@rivai.ai>
2023-04-26 12:22 ` Li, Pan2 [this message]
2023-04-26 13:06 ` [PATCH v2] " yanzhang.wang
2023-04-28 10:36 ` Li, Pan2
2023-05-02 15:35 ` Kito Cheng
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=SJ0PR11MB5919AB656AF2409335D67F6DA9659@SJ0PR11MB5919.namprd11.prod.outlook.com \
--to=pan2.li@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.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).