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 target/107160] [12 regression] r13-2641-g0ee1548d96884d causes verification failure in spec2006 Date: Mon, 17 Oct 2022 13:10:50 +0000 [thread overview] Message-ID: <bug-107160-4-wnI6T7H67J@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107160-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107160 --- Comment #19 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:d282dd56275485a88e1fe9c4ae1939b62d23b20b commit r12-8839-gd282dd56275485a88e1fe9c4ae1939b62d23b20b Author: Richard Biener <rguenther@suse.de> Date: Thu Oct 13 14:24:05 2022 +0200 tree-optimization/107160 - avoid reusing multiple accumulators Epilogue vectorization is not set up to re-use a vectorized accumulator consisting of more than one vector. For non-SLP we always reduce to a single but for SLP that isn't happening. In such case we currenlty miscompile the epilog so avoid this. PR tree-optimization/107160 * tree-vect-loop.cc (vect_create_epilog_for_reduction): Do not register accumulator if we failed to reduce it to a single vector. * gcc.dg/vect/pr107160.c: New testcase. (cherry picked from commit 5cbaf84c191b9a3e3cb26545c808d208bdbf2ab5)
next prev parent reply other threads:[~2022-10-17 13:10 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-05 16:21 [Bug target/107160] New: [13 " seurer at gcc dot gnu.org 2022-10-06 10:43 ` [Bug target/107160] " rguenth at gcc dot gnu.org 2022-10-06 14:04 ` seurer at gcc dot gnu.org 2022-10-06 19:08 ` seurer at gcc dot gnu.org 2022-10-10 2:29 ` linkw at gcc dot gnu.org 2022-10-10 19:14 ` seurer at gcc dot gnu.org 2022-10-12 8:31 ` linkw at gcc dot gnu.org 2022-10-13 9:57 ` linkw at gcc dot gnu.org 2022-10-13 10:16 ` rguenth at gcc dot gnu.org 2022-10-13 10:31 ` linkw at gcc dot gnu.org 2022-10-13 11:05 ` rguenther at suse dot de 2022-10-13 11:45 ` linkw at gcc dot gnu.org 2022-10-13 11:50 ` rguenther at suse dot de 2022-10-13 12:01 ` marxin at gcc dot gnu.org 2022-10-13 12:05 ` rguenth at gcc dot gnu.org 2022-10-13 12:23 ` rguenth at gcc dot gnu.org 2022-10-13 13:17 ` cvs-commit at gcc dot gnu.org 2022-10-13 13:19 ` [Bug target/107160] [12/13 " rguenth at gcc dot gnu.org 2022-10-14 2:54 ` [Bug target/107160] [12 " linkw at gcc dot gnu.org 2022-10-17 13:10 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-17 13:11 ` rguenth at gcc dot gnu.org
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-107160-4-wnI6T7H67J@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).