From: Segher Boessenkool <segher@kernel.crashing.org>
To: Surya Kumari Jangala <jskumari@linux.vnet.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Peter Bergner <bergner@linux.ibm.com>,
meissner@linux.ibm.com
Subject: Re: [PATCH] swap: Fix incorrect lane extraction by vec_extract() [PR106770]
Date: Mon, 27 Feb 2023 10:28:06 -0600 [thread overview]
Message-ID: <20230227162806.GY25951@gate.crashing.org> (raw)
In-Reply-To: <b6e8ab52-3c92-3fa0-c70a-085c5c53e18e@linux.vnet.ibm.com>
Hi!
On Wed, Jan 04, 2023 at 01:58:19PM +0530, Surya Kumari Jangala wrote:
> In the routine rs6000_analyze_swaps(), special handling of swappable
> instructions is done even if the webs that contain the swappable
> instructions are not optimized, i.e., the webs do not contain any
> permuting load/store instructions along with the associated register
> swap instructions. Doing special handling in such webs will result in
> the extracted lane being adjusted unnecessarily for vec_extract.
>
> Modifying swappable instructions is also incorrect in webs where
> loads/stores on quad word aligned addresses are changed to lvx/stvx.
> Similarly, in webs where swap(load(vector constant)) instructions are
> replaced with load(swapped vector constant), the swappable
> instructions should not be modified.
>
> 2023-01-04 Surya Kumari Jangala <jskumari@linux.ibm.com>
>
> gcc/
> PR rtl-optimization/106770
> * rs6000-p8swap.cc (rs6000_analyze_swaps): .
Please add an entry? Or multiple ones, actually. Describe all changes.
> --- a/gcc/config/rs6000/rs6000-p8swap.cc
> +++ b/gcc/config/rs6000/rs6000-p8swap.cc
> @@ -179,6 +179,9 @@ class swap_web_entry : public web_entry_base
> unsigned int special_handling : 4;
> /* Set if the web represented by this entry cannot be optimized. */
> unsigned int web_not_optimizable : 1;
> + /* Set if the web represented by this entry has been optimized, ie,
s/ie/i.e./
> + register swaps of permuting loads/stores have been removed. */
If it really means only exactly this, then the name isn't so good.
> + unsigned int web_is_optimized : 1;
And if it is as general as the name suggests, then the comment is no
good. Which is it? :-)
> /* For each load and store in an optimizable web (which implies
> the loads and stores are permuting), find the associated
> register swaps and mark them for removal. Due to various
> - optimizations we may mark the same swap more than once. Also
> - perform special handling for swappable insns that require it. */
> + optimizations we may mark the same swap more than once. Fix up
> + the non-permuting loads and stores by converting them into
> + permuting ones. */
Two spaces after a full stop is correct. Please put that back.
Is it a good idea convert from/to swapping load/stores in this pass at
all? Doesdn't that belong elsewhere? Like, in combine, where we
already should do this. Why does that not work?
> - if (!root_entry->web_not_optimizable)
> + if (!root_entry->web_not_optimizable) {
Blocks start on a new line, indented.
> mark_swaps_for_removal (insn_entry, i);
> + root_entry->web_is_optimized = true;
Indent using tabs where possible.
> + swap_web_entry* root_entry
> + = (swap_web_entry*)((&insn_entry[i])->unionfind_root ());
Space before *, in all cases. Space before the second (. There are too
many brackets here, too.
> + /* Perform special handling for swappable insns that require it.
No trailing spaces.
> + Note that special handling should be done only for those
> + swappable insns that are present in webs optimized above. */
> + for (i = 0; i < e; ++i)
> + if (insn_entry[i].is_swappable && insn_entry[i].special_handling &&
> + !(insn_entry[i].special_handling == SH_NOSWAP_LD ||
> + insn_entry[i].special_handling == SH_NOSWAP_ST))
> {
> swap_web_entry* root_entry
> = (swap_web_entry*)((&insn_entry[i])->unionfind_root ());
> - if (!root_entry->web_not_optimizable)
> + if (root_entry->web_is_optimized)
> handle_special_swappables (insn_entry, i);
> }
Why this change?
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/powerpc/pr106770.c
> @@ -0,0 +1,20 @@
> +/* { dg-do compile } */
> +/* { dg-require-effective-target powerpc_p8vector_ok } */
> +/* { dg-options "-mdejagnu-cpu=power8 -O3 " } */
Is -O3 required? Use -O2 if you can. And no trailing spaces please.
> +/* { dg-final { scan-assembler-times "xxpermdi" 2 } } */
Those two remaining are superfluous, so comment that please.
Segher
next prev parent reply other threads:[~2023-02-27 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 8:28 Surya Kumari Jangala
2023-01-12 16:51 ` [PING] " Surya Kumari Jangala
2023-02-17 5:08 ` [PING 2] " Surya Kumari Jangala
2023-02-27 11:52 ` [PING 3] " Surya Kumari Jangala
2023-02-27 16:28 ` Segher Boessenkool [this message]
2023-03-03 10:59 ` Surya Kumari Jangala
2023-03-03 17:19 ` Segher Boessenkool
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=20230227162806.GY25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jskumari@linux.vnet.ibm.com \
--cc=meissner@linux.ibm.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).