public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/40168] finding common subexpressions Date: Sat, 25 Dec 2021 07:01:19 +0000 [thread overview] Message-ID: <bug-40168-4-CkBBS4tFgR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-40168-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40168 --- Comment #22 from Andrew Pinski <pinskia at gcc dot gnu.org> --- With the trunk on the second testcase, SLP works but we get stuff like: _2 = (*b_420(D))[80]; _4 = (*b_420(D))[79]; _538 = {_2, _4}; _980 = _538 * vect__1.182_559; Shouldn't that just be loading a vector from (*b_420(D))[79] and then doing an VEC_PERM? In a reduced C testcase we get the correct thing: typedef double array[1000]; void f(array *a, array *b, array *c) { double t = (*a)[1] * (*b)[0]; double t1 = (*a)[0] * (*b)[0]; double t2 = (*a)[3] * (*b)[1]; double t3 = (*a)[2] * (*b)[1]; (*c)[0] = t; (*c)[1] = t1; (*c)[2] = t2; (*c)[3] = t3; }
prev parent reply other threads:[~2021-12-25 7:01 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-40168-4@http.gcc.gnu.org/bugzilla/> 2013-03-29 10:51 ` [Bug tree-optimization/40168] missing unrolling/scalarization/reassoc/free Joost.VandeVondele at mat dot ethz.ch 2021-12-25 7:01 ` pinskia at gcc dot gnu.org [this message]
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=bug-40168-4-CkBBS4tFgR@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).