From: "Li, Pan2" <pan2.li@intel.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "rguenther@suse.de" <rguenther@suse.de>,
"richard.sandiford@arm.com" <richard.sandiford@arm.com>
Subject: RE: [PATCH] GIMPLE_FOLD: Apply LEN_MASK_{LOAD, STORE} into GIMPLE_FOLD
Date: Sun, 25 Jun 2023 06:01:01 +0000 [thread overview]
Message-ID: <MW5PR11MB5908072C18272257D3A3EA9AA921A@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <e0c0f93b-3702-523b-da3f-4a711007d9c6@gmail.com>
Committed, thanks Jeff.
Pan
-----Original Message-----
From: Gcc-patches <gcc-patches-bounces+pan2.li=intel.com@gcc.gnu.org> On Behalf Of Jeff Law via Gcc-patches
Sent: Saturday, June 24, 2023 10:45 PM
To: juzhe.zhong@rivai.ai; gcc-patches@gcc.gnu.org
Cc: rguenther@suse.de; richard.sandiford@arm.com
Subject: Re: [PATCH] GIMPLE_FOLD: Apply LEN_MASK_{LOAD, STORE} into GIMPLE_FOLD
On 6/23/23 07:48, juzhe.zhong@rivai.ai wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> Hi, since we are going to have LEN_MASK_{LOAD,STORE} into loopVectorizer.
>
> Currenly,
> 1. we can fold MASK_{LOAD,STORE} into MEM when mask is all ones.
> 2. we can fold LEN_{LOAD,STORE} into MEM when (len - bias) is VF.
>
> Now, I think it makes sense that we can support
>
> fold LEN_MASK_{LOAD,STORE} into MEM when both mask = all ones and (len - bias) is VF.
>
> gcc/ChangeLog:
>
> * gimple-fold.cc (arith_overflowed_p): Apply LEN_MASK_{LOAD,STORE}.
> (gimple_fold_partial_load_store_mem_ref): Ditto.
> (gimple_fold_partial_store): Ditto.
> (gimple_fold_call): Ditto.
OK
jeff
prev parent reply other threads:[~2023-06-25 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 13:48 [PATCH] GIMPLE_FOLD: Apply LEN_MASK_{LOAD,STORE} " juzhe.zhong
2023-06-24 14:44 ` Jeff Law
2023-06-25 6:01 ` 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=MW5PR11MB5908072C18272257D3A3EA9AA921A@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 \
--cc=richard.sandiford@arm.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).