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/114297] [14 Regression] Yet more problems with "definition in block does not dominate use in block" Date: Tue, 12 Mar 2024 07:17:26 +0000 [thread overview] Message-ID: <bug-114297-4-rAPJJ9jdsc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114297-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114297 --- Comment #3 from GCC 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:c0c57246d5b47459bdb488734bc2c004a92668b5 commit r14-9435-gc0c57246d5b47459bdb488734bc2c004a92668b5 Author: Richard Biener <rguenther@suse.de> Date: Mon Mar 11 14:58:57 2024 +0100 tree-optimization/114297 - SLP reduction with early break fix The following makes sure to pass in the SLP node for the live stmts we are generating the reduction epilogue for to vect_create_epilog_for_reduction. This follows the previous fix for the non-SLP path. PR tree-optimization/114297 * tree-vect-loop.cc (vectorizable_live_operation): Pass in the live stmts SLP node to vect_create_epilog_for_reduction. * gcc.dg/vect/vect-early-break_123-pr114297.c: New testcase.
next prev parent reply other threads:[~2024-03-12 7:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-10 15:11 [Bug c++/114297] New: " dcb314 at hotmail dot com 2024-03-10 18:29 ` [Bug tree-optimization/114297] [14 Regression] " pinskia at gcc dot gnu.org 2024-03-10 18:38 ` pinskia at gcc dot gnu.org 2024-03-11 8:11 ` rguenth at gcc dot gnu.org 2024-03-12 7:17 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-12 7:17 ` 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-114297-4-rAPJJ9jdsc@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).