public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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, 09 Jun 2021 12:41:50 +0000 [thread overview] Message-ID: <bug-97832-4-Lbgf0rWcHm@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 #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:ce670e4faafb296d1f1a7828d20f8c8ba4686797 commit r12-1329-gce670e4faafb296d1f1a7828d20f8c8ba4686797 Author: Richard Biener <rguenther@suse.de> Date: Wed Nov 18 14:17:34 2020 +0100 tree-optimization/97832 - handle associatable chains in SLP discovery This makes SLP discovery handle associatable (including mixed plus/minus) chains better by swapping operands across the whole chain. To work this adds caching of the 'matches' lanes for failed SLP discovery attempts, thereby fixing a failed SLP discovery for the slp-pr98855.cc testcase which results in building an operand from scalars as expected. Unfortunately this makes us trip over the cost threshold so I'm XFAILing the testcase for now. For BB vectorization all this doesn't work because we have no way to distinguish good from bad associations as we eventually build operands from scalars and thus not fail in the classical sense. 2021-05-31 Richard Biener <rguenther@suse.de> PR tree-optimization/97832 * tree-vectorizer.h (_slp_tree::failed): New. * tree-vect-slp.c (_slp_tree::_slp_tree): Initialize failed member. (_slp_tree::~_slp_tree): Free failed. (vect_build_slp_tree): Retain failed nodes and record matches in them, copying that back out when running into a cached fail. Dump start and end of discovery. (dt_sort_cmp): New. (vect_build_slp_tree_2): Handle associatable chains together doing more aggressive operand swapping. * gcc.dg/vect/pr97832-1.c: New testcase. * gcc.dg/vect/pr97832-2.c: Likewise. * gcc.dg/vect/pr97832-3.c: Likewise. * g++.dg/vect/slp-pr98855.cc: XFAIL.
next prev parent reply other threads:[~2021-06-09 12:41 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 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 [this message] 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-Lbgf0rWcHm@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).