From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: will schmidt <will_schmidt@vnet.ibm.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2] rs6000: Add load density heuristic
Date: Mon, 6 Sep 2021 18:43:09 -0500 [thread overview]
Message-ID: <20210906234308.GD1583@gate.crashing.org> (raw)
In-Reply-To: <91063938-9ac4-93ed-c438-abf25d4eca05@linux.ibm.com>
Hi!
On Wed, Jul 28, 2021 at 10:59:50AM +0800, Kewen.Lin wrote:
> >> +/* As a visitor function for each statement cost entry handled in
> >> + function add_stmt_cost, gather some information and update its
> >> + relevant fields in target cost accordingly. */
> >
> > I got lost trying to parse that.. (could be just me :-)
> >
> > Possibly instead something like
> > /* Helper function for add_stmt_cost ; gather information and update
> > the target_cost fields accordingly. */
>
> OK, will update. I was thinking for each entry handled in function
> add_stmt_cost, this helper acts like a visitor, trying to visit each
> entry and take some actions if some conditions are satisifed.
It (thankfully!) has nothing to do with the "visitor pattern", so some
other name might be better :-)
> > Maybe clearer to read if you rearrange slightly and flatten it ? I
> > defer to others on that..
> >
> > if ((kind == vec_to_scalar
> > || kind == vec_perm
> > || kind == vec_promote_demote
> > || kind == vec_construct
> > || kind == scalar_to_vec)
> > || (kind == vector_stmt && where == vect_body)
>
> This hunk is factored out from function rs6000_add_stmt_cost, maybe I
> can keep the original formatting? The formatting tool isn't so smart,
> and sometimes rearrange things to become unexpected (although it meets
> the basic rule, not so elegant), sigh.
It has too many parens, making grouping where there is none, that is the
core issue.
if (kind == vec_to_scalar
|| kind == vec_perm
|| kind == vec_promote_demote
|| kind == vec_construct
|| kind == scalar_to_vec
|| (kind == vector_stmt && where == vect_body))
Segher
next prev parent reply other threads:[~2021-09-06 23:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 2:29 [PATCH] rs6000: Adjust rs6000_density_test for strided_load Kewen.Lin
2021-05-26 2:59 ` [PATCH v2] rs6000: Add load density heuristic Kewen.Lin
2021-06-09 2:26 ` PING^1 " Kewen.Lin
2021-06-28 7:01 ` PING^2 " Kewen.Lin
2021-07-15 1:59 ` PING^3 " Kewen.Lin
2021-07-27 22:25 ` will schmidt
2021-07-28 2:59 ` Kewen.Lin
2021-09-06 23:43 ` Segher Boessenkool [this message]
2021-09-08 7:01 ` Kewen.Lin
2021-07-28 5:22 ` [PATCH v3] " Kewen.Lin
2021-09-03 15:57 ` Bill Schmidt
2021-09-08 6:57 ` [PATCH v4] " Kewen.Lin
2021-09-08 8:28 ` Kewen.Lin
2021-09-09 16:11 ` Segher Boessenkool
2021-09-09 17:19 ` Bill Schmidt
2021-09-09 17:39 ` Bill Schmidt
2021-09-09 18:24 ` Segher Boessenkool
2021-09-10 3:22 ` Kewen.Lin
2021-09-10 3:46 ` Kewen.Lin
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=20210906234308.GD1583@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=will_schmidt@vnet.ibm.com \
--cc=wschmidt@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).