public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: "Laurent Thévenoux" <lrnt@thvnx.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: How to gimplify_build a FMA_EXPR since it was removed?
Date: Mon, 04 Feb 2019 23:34:00 -0000	[thread overview]
Message-ID: <CA+=Sn1kbNPKN6UdjQj_HH0+odtzoRvXsgJt_e2sOQwPAvn-ACg@mail.gmail.com> (raw)
In-Reply-To: <0A4AE13B-24BF-4818-BFE9-1C4999C77A36@thvnx.com>

On Mon, Feb 4, 2019 at 3:13 PM Laurent Thévenoux <lrnt@thvnx.com> wrote:
>
> Hi,
>
> Thanks for pointing this me out. Nevertheless, I’m not sure this can apply in my case since gimple_build_call_internal() returns a gimple data type while gimplify_build3() returns a tree data type. I’ll try to figure how faisable is to use it in my case. For more context, see the code snippet below.

You need to create a new temp ssa name to hold the FMA results.  There
are few examples in the tree-ssa-phi-opt.c code for on how to use this
way instead of using gimplify_build3.

Thanks,
Andrew Pinski

>
> ```
> static void
> some_fn (gimple_stmt_iterator *gsi, tree inner_type, tree ar, tree ai, tree br, tree bi)
> {
>   tree rr, ri, pr1;
>
>   p1r = gimplify_build2 (gsi, MULT_EXPR, inner_type, ar, ar);
>   rr  = gimplify_build3 (gsi, FMA_EXPR, inner_type, ai, ai, p1r);
>   ri  = build_real (inner_type, dconst0);
>   update_complex_assignment (gsi, rr, ri);
> }
>
> ```
>
> > Le 4 févr. 2019 à 23:38, Andrew Pinski <pinskia@gmail.com> a écrit :
> >
> > On Mon, Feb 4, 2019 at 4:47 AM Laurent Thévenoux <lrnt@thvnx.com> wrote:
> >>
> >> Sorry for duplicate, gcc-help was not the right mailing list for this one.
> >>
> >>
> >> -------- Original Message --------
> >> Subject: How to gimplify_build a FMA_EXPR since it was removed?
> >> Date: Monday, February 04, 2019 13:28 CET
> >> From: Laurent Thévenoux <lrnt@thvnx.com>
> >> To: gcc-help@gcc.gnu.org
> >> CC: richard.sandiford@linaro.org
> >>
> >>
> >>
> >> Hi,
> >>
> >> I've developed some code in gcc/tree-complex.c. I was using the
> >> FMA_EXPR to generate fma operations such as in:
> >>
> >> ```
> >> rr  = gimplify_build3 (gsi, FMA_EXPR, inner_type, ai, ai, p1r);```
> >>
> >> FMA_EXPR was removed in https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00570.html.
> >>
> >> Is there an easy way to gimplify FMAs with the new functions
> >> introduced in the patch below?
> >
> > From that patch (e.g. rs6000_gimple_fold_builtin):
> >
> > - gimple *g = gimple_build_assign (lhs, FMA_EXPR, arg0, arg1, arg2);
> > + gcall *g = gimple_build_call_internal (IFN_FMA, 3, arg0, arg1, arg2);
> > + gimple_call_set_lhs (g, lhs);
> > + gimple_call_set_nothrow (g, true);
> >
> >
> > Thanks,
> > Andrew Pinski
> >
> >
> >>
> >> Thanks,
> >> Laurent
>

  reply	other threads:[~2019-02-04 23:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 12:46 Fwd: " Laurent Thévenoux
2019-02-04 22:38 ` Andrew Pinski
2019-02-04 23:13   ` Laurent Thévenoux
2019-02-04 23:34     ` Andrew Pinski [this message]
2019-02-06 18:21       ` Laurent Thévenoux

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='CA+=Sn1kbNPKN6UdjQj_HH0+odtzoRvXsgJt_e2sOQwPAvn-ACg@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=lrnt@thvnx.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).