public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-1085] middle-end/105965 - add missing v_c_e <{ el }> simplification Date: Tue, 14 Jun 2022 10:53:07 +0000 (GMT) [thread overview] Message-ID: <20220614105307.9DE10385AE5F@sourceware.org> (raw) https://gcc.gnu.org/g:90467f0ad649d0817f9e034596a0fb85605b55af commit r13-1085-g90467f0ad649d0817f9e034596a0fb85605b55af Author: Richard Biener <rguenther@suse.de> Date: Tue Jun 14 10:59:49 2022 +0200 middle-end/105965 - add missing v_c_e <{ el }> simplification When we got the simplification of bit-field-ref to view-convert we lost the ability to detect FMAs since we cannot look through _1 = {_10}; _11 = VIEW_CONVERT_EXPR<float>(_1); the following amends the (view_convert CONSTRUCTOR) pattern to handle this case. 2022-06-14 Richard Biener <rguenther@suse.de> PR middle-end/105965 * match.pd (view_convert CONSTRUCTOR): Handle single-element CTOR case. * gcc.target/i386/pr105965.c: New testcase. Diff: --- gcc/match.pd | 17 +++++++++++++---- gcc/testsuite/gcc.target/i386/pr105965.c | 12 ++++++++++++ 2 files changed, 25 insertions(+), 4 deletions(-) diff --git a/gcc/match.pd b/gcc/match.pd index 44a385b912d..776c9c6489a 100644 --- a/gcc/match.pd +++ b/gcc/match.pd @@ -3669,12 +3669,21 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT) && TYPE_UNSIGNED (TREE_TYPE (@1))))) (view_convert @1))) -/* Simplify a view-converted empty constructor. */ +/* Simplify a view-converted empty or single-element constructor. */ (simplify (view_convert CONSTRUCTOR@0) - (if (TREE_CODE (@0) != SSA_NAME - && CONSTRUCTOR_NELTS (@0) == 0) - { build_zero_cst (type); })) + (with + { tree ctor = (TREE_CODE (@0) == SSA_NAME + ? gimple_assign_rhs1 (SSA_NAME_DEF_STMT (@0)) : @0); } + (switch + (if (CONSTRUCTOR_NELTS (ctor) == 0) + { build_zero_cst (type); }) + (if (CONSTRUCTOR_NELTS (ctor) == 1 + && VECTOR_TYPE_P (TREE_TYPE (ctor)) + && operand_equal_p (TYPE_SIZE (type), + TYPE_SIZE (TREE_TYPE + (CONSTRUCTOR_ELT (ctor, 0)->value)))) + (view_convert { CONSTRUCTOR_ELT (ctor, 0)->value; }))))) /* Re-association barriers around constants and other re-association barriers can be removed. */ diff --git a/gcc/testsuite/gcc.target/i386/pr105965.c b/gcc/testsuite/gcc.target/i386/pr105965.c new file mode 100644 index 00000000000..5bb53790de8 --- /dev/null +++ b/gcc/testsuite/gcc.target/i386/pr105965.c @@ -0,0 +1,12 @@ +/* { dg-do compile } */ +/* { dg-options "-O2 -mfma -mfpmath=sse" } */ + +typedef float v1sf __attribute__((vector_size(4))); + +v1sf +foo43 (v1sf a, v1sf b, v1sf c) +{ + return a * b + c; +} + +/* { dg-final { scan-assembler "fmadd" } } */
reply other threads:[~2022-06-14 10:53 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=20220614105307.9DE10385AE5F@sourceware.org \ --to=rguenth@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).