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>,
"rdapp.gcc@gmail.com" <rdapp.gcc@gmail.com>
Subject: RE: [PATCH] RISC-V Regression: Make match patterns more accurate
Date: Tue, 10 Oct 2023 14:02:30 +0000 [thread overview]
Message-ID: <MW5PR11MB590836C20178C5754FC883FFA9CDA@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2e16bc3c-129e-4a40-9484-58c5de6541a8@gmail.com>
Committed, thanks Jeff.
Pan
-----Original Message-----
From: Jeff Law <jeffreyalaw@gmail.com>
Sent: Tuesday, October 10, 2023 9:47 PM
To: Juzhe-Zhong <juzhe.zhong@rivai.ai>; gcc-patches@gcc.gnu.org
Cc: rguenther@suse.de; rdapp.gcc@gmail.com
Subject: Re: [PATCH] RISC-V Regression: Make match patterns more accurate
On 10/9/23 20:47, Juzhe-Zhong wrote:
> This patch fixes following 2 FAILs in RVV regression since the check is not accurate.
>
> It's inspired by Robin's previous patch:
> https://patchwork.sourceware.org/project/gcc/patch/dde89b9e-49a0-d70b-0906-fb3022cac11b@gmail.com/
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/vect/no-scevccp-outer-7.c: Adjust regex pattern.
> * gcc.dg/vect/no-scevccp-vect-iv-3.c: Ditto.
OK. We might see other ports flipping to a pass if they were
exhibiting the same behavior with failing to vectorize with the first
selected type, but passing on the second type.
Jeff
prev parent reply other threads:[~2023-10-10 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 2:47 Juzhe-Zhong
2023-10-10 13:46 ` Jeff Law
2023-10-10 14:02 ` 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=MW5PR11MB590836C20178C5754FC883FFA9CDA@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=rdapp.gcc@gmail.com \
--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).