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/113178] [14 Regression] ice in find_uses_to_rename_use Date: Fri, 12 Jan 2024 15:32:51 +0000 [thread overview] Message-ID: <bug-113178-4-z7adQNImuS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113178-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113178 --- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>: https://gcc.gnu.org/g:e79c5855ab39d96baa7c6bec63eb97715abcf68d commit r14-7197-ge79c5855ab39d96baa7c6bec63eb97715abcf68d Author: Tamar Christina <tamar.christina@arm.com> Date: Fri Jan 12 15:26:29 2024 +0000 middle-end: fill in reduction PHI for all alt exits [PR113178] When we have a loop with more than 2 exits and a reduction I forgot to fill in the PHI value for all alternate exits. All alternate exits use the same PHI value so we should loop over the new PHI elements and copy the value across since we call the reduction calculation code only once for all exits. This was normally covered up by earlier parts of the compiler rejecting loops incorrectly (which has been fixed now). Note that while I can use the loop in all cases, the reason I separated out the main and alt exit is so that if you pass the wrong edge the macro will assert. gcc/ChangeLog: PR tree-optimization/113178 * tree-vect-loop.cc (vect_create_epilog_for_reduction): Fill in all alternate exits. gcc/testsuite/ChangeLog: PR tree-optimization/113178 * gcc.dg/vect/vect-early-break_101-pr113178.c: New test. * gcc.dg/vect/vect-early-break_102-pr113178.c: New test.
next prev parent reply other threads:[~2024-01-12 15:32 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-30 10:15 [Bug c++/113178] New: " dcb314 at hotmail dot com 2023-12-30 18:36 ` [Bug tree-optimization/113178] [14 Regression] " pinskia at gcc dot gnu.org 2023-12-30 18:46 ` pinskia at gcc dot gnu.org 2023-12-30 19:38 ` dcb314 at hotmail dot com 2023-12-30 20:28 ` dcb314 at hotmail dot com 2023-12-30 20:56 ` dcb314 at hotmail dot com 2024-01-02 10:09 ` tnfchris at gcc dot gnu.org 2024-01-10 13:27 ` rguenth at gcc dot gnu.org 2024-01-10 18:02 ` jamborm at gcc dot gnu.org 2024-01-12 15:32 ` cvs-commit at gcc dot gnu.org 2024-01-12 15:32 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-12 15:36 ` tnfchris 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-113178-4-z7adQNImuS@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).