From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Jakub Jelinek <jakub@gcc.gnu.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Di Zhao OS <dizhao@os.amperecomputing.com>
Subject: Re: [PATCH v2] tree-optimization/110279- Check for nested FMA chains in reassoc
Date: Tue, 11 Jul 2023 08:51:11 +0200 [thread overview]
Message-ID: <CAAeLtUCCHusmtM3Op17qsueDf_N1y6WHUW6DCt5zGx3muX44vw@mail.gmail.com> (raw)
In-Reply-To: <SN6PR01MB4240D86D91F517459328C1A8E831A@SN6PR01MB4240.prod.exchangelabs.com>
Jakub,
it looks like you did a lot of work on reassoc in the past — could you
have a quick look and comment?
Thanks,
Philipp.
On Tue, 11 Jul 2023 at 04:59, Di Zhao OS <dizhao@os.amperecomputing.com> wrote:
>
> Attached is an updated version of the patch.
>
> Based on Philipp's review, some changes:
>
> 1. Defined new enum fma_state to describe the state of FMA candidates
> for a list of operands. (Since the tests seems simple after the
> change, I didn't add predicates on it.)
> 2. Changed return type of convert_mult_to_fma_1 and convert_mult_to_fma
> to tree, to remove the in/out parameter.
> 3. Added description of return value values of rank_ops_for_fma.
>
> ---
> gcc/ChangeLog:
>
> * tree-ssa-math-opts.cc (convert_mult_to_fma_1): Added new parameter
> check_only_p. Changed return type to tree.
> (struct fma_transformation_info): Moved to header.
> (class fma_deferring_state): Moved to header.
> (convert_mult_to_fma): Added new parameter check_only_p. Changed
> return type to tree.
> * tree-ssa-math-opts.h (struct fma_transformation_info): Moved from .cc.
> (class fma_deferring_state): Moved from .cc.
> (convert_mult_to_fma): Add function decl.
> * tree-ssa-reassoc.cc (enum fma_state): Defined new enum to describe
> the state of FMA candidates for a list of operands.
> (rewrite_expr_tree_parallel): Changed boolean parameter to enum type.
> (rank_ops_for_fma): Return enum fma_state.
> (reassociate_bb): Avoid rewriting to parallel if nested FMAs are found.
>
> Thanks,
> Di Zhao
>
>
next prev parent reply other threads:[~2023-07-11 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 2:59 Di Zhao OS
2023-07-11 6:51 ` Philipp Tomsich [this message]
2023-07-17 14:25 ` Tamar Christina
2023-07-18 11:41 ` Richard Biener
2023-07-19 9:05 ` Richard Biener
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=CAAeLtUCCHusmtM3Op17qsueDf_N1y6WHUW6DCt5zGx3muX44vw@mail.gmail.com \
--to=philipp.tomsich@vrull.eu \
--cc=dizhao@os.amperecomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@gcc.gnu.org \
/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).