public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Tamar Christina <tnfchris@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6618] middle-end: don't form FMAs when multiplication is not single use. [PR108583] Date: Sun, 12 Mar 2023 18:43:55 +0000 (GMT) [thread overview] Message-ID: <20230312184355.7AAA3385843D@sourceware.org> (raw) https://gcc.gnu.org/g:0b3c630fcc44063a61f6131af48a4171b1de2b37 commit r13-6618-g0b3c630fcc44063a61f6131af48a4171b1de2b37 Author: Tamar Christina <tamar.christina@arm.com> Date: Sun Mar 12 18:40:50 2023 +0000 middle-end: don't form FMAs when multiplication is not single use. [PR108583] The testcase typedef unsigned int vec __attribute__((vector_size(32))); vec f3 (vec a, vec b, vec c) { vec d = a * b; return d + ((c + d) >> 1); } shows a case where we don't want to form an FMA due to the MUL not being single use. In this case to form an FMA we have to redo the MUL as well as we no longer have it to share. As such making an FMA here would be a de-optimization. gcc/ChangeLog: PR target/108583 * tree-ssa-math-opts.cc (convert_mult_to_fma): Inhibit FMA in case not single use. gcc/testsuite/ChangeLog: PR target/108583 * gcc.dg/mla_1.c: New test. Co-Authored-By: Richard Sandiford <richard.sandiford@arm.com> Diff: --- gcc/testsuite/gcc.dg/mla_1.c | 40 ++++++++++++++++++++++++++++++++++++++++ gcc/tree-ssa-math-opts.cc | 14 ++++++++++++++ 2 files changed, 54 insertions(+) diff --git a/gcc/testsuite/gcc.dg/mla_1.c b/gcc/testsuite/gcc.dg/mla_1.c new file mode 100644 index 00000000000..98e5808ee70 --- /dev/null +++ b/gcc/testsuite/gcc.dg/mla_1.c @@ -0,0 +1,40 @@ +/* { dg-do compile } */ +/* { dg-require-effective-target vect_int } */ +/* { dg-options "-O2 -msve-vector-bits=256 -march=armv8.2-a+sve -fdump-tree-optimized" { target aarch64*-*-* } } */ + +unsigned int +f1 (unsigned int a, unsigned int b, unsigned int c) { + unsigned int d = a * b; + return d + ((c + d) >> 1); +} + +unsigned int +g1 (unsigned int a, unsigned int b, unsigned int c) { + return a * b + c; +} + +__Uint32x4_t +f2 (__Uint32x4_t a, __Uint32x4_t b, __Uint32x4_t c) { + __Uint32x4_t d = a * b; + return d + ((c + d) >> 1); +} + +__Uint32x4_t +g2 (__Uint32x4_t a, __Uint32x4_t b, __Uint32x4_t c) { + return a * b + c; +} + +typedef unsigned int vec __attribute__((vector_size(32))); vec +f3 (vec a, vec b, vec c) +{ + vec d = a * b; + return d + ((c + d) >> 1); +} + +vec +g3 (vec a, vec b, vec c) +{ + return a * b + c; +} + +/* { dg-final { scan-tree-dump-times {\.FMA } 1 "optimized" { target aarch64*-*-* } } } */ diff --git a/gcc/tree-ssa-math-opts.cc b/gcc/tree-ssa-math-opts.cc index 5ab5b944a57..26ed91d58fa 100644 --- a/gcc/tree-ssa-math-opts.cc +++ b/gcc/tree-ssa-math-opts.cc @@ -3346,6 +3346,20 @@ convert_mult_to_fma (gimple *mul_stmt, tree op1, tree op2, param_avoid_fma_max_bits)); bool defer = check_defer; bool seen_negate_p = false; + + /* There is no numerical difference between fused and unfused integer FMAs, + and the assumption below that FMA is as cheap as addition is unlikely + to be true, especially if the multiplication occurs multiple times on + the same chain. E.g., for something like: + + (((a * b) + c) >> 1) + (a * b) + + we do not want to duplicate the a * b into two additions, not least + because the result is not a natural FMA chain. */ + if (ANY_INTEGRAL_TYPE_P (type) + && !has_single_use (mul_result)) + return false; + /* Make sure that the multiplication statement becomes dead after the transformation, thus that all uses are transformed to FMAs. This means we assume that an FMA operation has the same cost
reply other threads:[~2023-03-12 18:43 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230312184355.7AAA3385843D@sourceware.org \ --to=tnfchris@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).