From: "Li, Pan2" <pan2.li@intel.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
Juzhe-Zhong <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>,
"rdapp.gcc@gmail.com" <rdapp.gcc@gmail.com>
Subject: RE: [PATCH] RISC-V: Fix AVL_TYPE attribute of tuple mode mov<mode>
Date: Mon, 23 Oct 2023 02:26:53 +0000 [thread overview]
Message-ID: <MW5PR11MB59080E0D79C6694584E3130FA9D8A@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2b2e1cab-fed1-496a-b641-501539937d85@gmail.com>
Committed, thanks Jeff.
Pan
-----Original Message-----
From: Jeff Law <jeffreyalaw@gmail.com>
Sent: Monday, October 23, 2023 10:24 AM
To: Juzhe-Zhong <juzhe.zhong@rivai.ai>; gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com; kito.cheng@sifive.com; rdapp.gcc@gmail.com
Subject: Re: [PATCH] RISC-V: Fix AVL_TYPE attribute of tuple mode mov<mode>
On 10/22/23 16:46, Juzhe-Zhong wrote:
> The tuple mode mov<mode> pattern doesn't have avl_type so it is invalid attribute.
>
> gcc/ChangeLog:
>
> * config/riscv/vector.md: Fix avl_type attribute of tuple mov<mode>.
Presumably you got a fault or something similar trying to compute the
avl_type attr when trying to access operands[7]? from this code:
> (eq_attr "type" "vlde,vldff,vste,vimov,vimov,vimov,vfmov,vext,vimerge,\
> vfsqrt,vfrecp,vfmerge,vfcvtitof,vfcvtftoi,vfwcvtitof,\
> vfwcvtftoi,vfwcvtftof,vfncvtitof,vfncvtftoi,vfncvtftof,\
> vfclass,vired,viwred,vfredu,vfredo,vfwredu,vfwredo,\
> vimovxv,vfmovfv,vlsegde,vlsegdff")
> (symbol_ref "INTVAL (operands[7])")
> (eq_attr "type" "vldm,vstm,vimov,vmalu,vmalu")
OK for the trunk.
Jeff
next prev parent reply other threads:[~2023-10-23 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 22:46 Juzhe-Zhong
2023-10-23 2:24 ` Jeff Law
2023-10-23 2:26 ` Li, Pan2 [this message]
2023-10-23 2:32 ` juzhe.zhong
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=MW5PR11MB59080E0D79C6694584E3130FA9D8A@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=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).