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: "rguenther@suse.de" <rguenther@suse.de>
Subject: RE: [PATCH] RISC-V Regression: Fix FAIL of vect-multitypes-16.c for RVV
Date: Wed, 11 Oct 2023 01:08:43 +0000 [thread overview]
Message-ID: <MW5PR11MB59089C24A111DCAE5812FAD8A9CCA@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <30311131-1fb1-4926-b66f-a5e94eb1e17b@gmail.com>
Committed, thanks Jeff.
Pan
-----Original Message-----
From: Jeff Law <jeffreyalaw@gmail.com>
Sent: Tuesday, October 10, 2023 11:29 PM
To: Juzhe-Zhong <juzhe.zhong@rivai.ai>; gcc-patches@gcc.gnu.org
Cc: rguenther@suse.de
Subject: Re: [PATCH] RISC-V Regression: Fix FAIL of vect-multitypes-16.c for RVV
On 10/10/23 08:49, Juzhe-Zhong wrote:
> As Richard suggested: https://gcc.gnu.org/pipermail/gcc-patches/2023-October/632288.html
>
> Add vect_ext_char_longlong to fix FAIL for RVV.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/vect/vect-multitypes-16.c: Adapt check for RVV.
> * lib/target-supports.exp: Add vect_ext_char_longlong property.
OK
jeff
prev parent reply other threads:[~2023-10-11 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 14:49 Juzhe-Zhong
2023-10-10 15:28 ` Jeff Law
2023-10-11 1:08 ` 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=MW5PR11MB59089C24A111DCAE5812FAD8A9CCA@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=rguenther@suse.de \
/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).