public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97832] AoSoA complex caxpy-like loops: AVX2+FMA -Ofast 7 times slower than -O3 Date: Wed, 18 Nov 2020 13:39:57 +0000 [thread overview] Message-ID: <bug-97832-4-XwEo1EmBDp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97832-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97832 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- There's then also a permute optimization left on the plate: t.c:16:3: note: node 0x3a19590 (max_nunits=4, refcnt=2) t.c:16:3: note: stmt 0 _153 = f11_im_76 * x1_im_142; t.c:16:3: note: stmt 1 _213 = f11_re_72 * x1_re_202; t.c:16:3: note: stmt 2 _275 = f11_re_72 * x1_re_264; t.c:16:3: note: stmt 3 _337 = f11_re_72 * x1_re_326; t.c:16:3: note: stmt 4 _155 = f11_im_76 * x1_re_140; t.c:16:3: note: stmt 5 _217 = f11_im_76 * x1_re_202; t.c:16:3: note: stmt 6 _279 = f11_im_76 * x1_re_264; t.c:16:3: note: stmt 7 _341 = f11_im_76 * x1_re_326; t.c:16:3: note: children 0x3a19600 0x3a19670 t.c:16:3: note: node (external) 0x3a19600 (max_nunits=1, refcnt=1) t.c:16:3: note: { f11_im_76, f11_re_72, f11_re_72, f11_re_72, f11_im_76, f11_im_76, f11_im_76, f11_im_76 } t.c:16:3: note: node 0x3a19670 (max_nunits=4, refcnt=1) t.c:16:3: note: stmt 0 x1_im_142 = *_141; t.c:16:3: note: stmt 1 x1_re_202 = *_201; t.c:16:3: note: stmt 2 x1_re_264 = *_263; t.c:16:3: note: stmt 3 x1_re_326 = *_325; t.c:16:3: note: stmt 4 x1_re_140 = *_139; t.c:16:3: note: stmt 5 x1_re_202 = *_201; t.c:16:3: note: stmt 6 x1_re_264 = *_263; t.c:16:3: note: stmt 7 x1_re_326 = *_325; t.c:16:3: note: load permutation { 4 1 2 3 0 1 2 3 } which we currently do not handle (there's a FIXME as to permute externals, currently we only handle splats as transparent for permutes).
next prev parent reply other threads:[~2020-11-18 13:39 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-14 20:44 [Bug target/97832] New: " already5chosen at yahoo dot com 2020-11-16 7:21 ` [Bug target/97832] " rguenth at gcc dot gnu.org 2020-11-16 11:11 ` rguenth at gcc dot gnu.org 2020-11-16 20:11 ` already5chosen at yahoo dot com 2020-11-17 9:21 ` [Bug tree-optimization/97832] " rguenth at gcc dot gnu.org 2020-11-17 10:18 ` rguenth at gcc dot gnu.org 2020-11-18 8:53 ` rguenth at gcc dot gnu.org 2020-11-18 9:15 ` rguenth at gcc dot gnu.org 2020-11-18 13:23 ` rguenth at gcc dot gnu.org 2020-11-18 13:39 ` rguenth at gcc dot gnu.org [this message] 2020-11-19 19:55 ` already5chosen at yahoo dot com 2020-11-20 7:10 ` rguenth at gcc dot gnu.org 2021-06-09 12:41 ` cvs-commit at gcc dot gnu.org 2021-06-09 12:54 ` rguenth at gcc dot gnu.org 2022-01-21 0:16 ` pinskia at gcc dot gnu.org 2022-11-24 23:22 ` already5chosen at yahoo dot com 2022-11-25 8:16 ` rguenth at gcc dot gnu.org 2022-11-25 13:19 ` already5chosen at yahoo dot com 2022-11-25 20:46 ` rguenth at gcc dot gnu.org 2022-11-25 21:27 ` amonakov at gcc dot gnu.org 2022-11-26 18:27 ` already5chosen at yahoo dot com 2022-11-26 18:36 ` already5chosen at yahoo dot com 2022-11-26 19:36 ` amonakov at gcc dot gnu.org 2022-11-26 22:00 ` already5chosen at yahoo dot com 2022-11-28 6:29 ` crazylht at gmail dot com 2022-11-28 6:42 ` crazylht at gmail dot com 2022-11-28 7:21 ` rguenther at suse dot de 2022-11-28 7:24 ` crazylht at gmail dot com
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-97832-4-XwEo1EmBDp@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).