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/113374] [14 regression] ICE in find_uses_to_rename_use
Date: Thu, 18 Jan 2024 07:37:17 +0000 [thread overview]
Message-ID: <bug-113374-4-rACRSr4zjP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113374-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113374
--- Comment #10 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:0f38666680d6ad0e40c4a8b6d94b2c93931cdf42
commit r14-8206-g0f38666680d6ad0e40c4a8b6d94b2c93931cdf42
Author: Richard Biener <rguenther@suse.de>
Date: Wed Jan 17 13:24:22 2024 +0100
tree-optimization/113374 - early break vect and virtual operands
The following fixes wrong virtual operands being used for peeled
early breaks where we can have different live ones and for multiple
exits it makes sure to update the correct PHI arguments.
I've introduced SET_PHI_ARG_DEF_ON_EDGE so we can avoid using
a wrong edge to compute the PHI arg index from.
I've took the liberty to understand the code again and refactor
and comment it a bit differently. The main functional change
is that we preserve the live virtual operand on all exits.
PR tree-optimization/113374
* tree-ssa-operands.h (SET_PHI_ARG_DEF_ON_EDGE): New.
* tree-vect-loop.cc (move_early_exit_stmts): Update
virtual LC PHIs.
* tree-vect-loop-manip.cc (slpeel_tree_duplicate_loop_to_edge_cfg):
Refactor. Preserve virtual LC PHIs on all exits.
* gcc.dg/vect/vect-early-break_106-pr113374.c: New testcase.
next prev parent reply other threads:[~2024-01-18 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 9:58 [Bug c++/113374] New: new breakage " dcb314 at hotmail dot com
2024-01-13 14:50 ` [Bug tree-optimization/113374] [14 regression] ICE " dcb314 at hotmail dot com
2024-01-13 16:14 ` pinskia at gcc dot gnu.org
2024-01-13 20:42 ` pinskia at gcc dot gnu.org
2024-01-13 22:50 ` pinskia at gcc dot gnu.org
2024-01-13 22:50 ` pinskia at gcc dot gnu.org
2024-01-15 8:33 ` rguenth at gcc dot gnu.org
2024-01-15 8:44 ` jakub at gcc dot gnu.org
2024-01-15 9:08 ` jakub at gcc dot gnu.org
2024-01-15 16:51 ` jakub at gcc dot gnu.org
2024-01-16 14:49 ` rguenth at gcc dot gnu.org
2024-01-18 7:37 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-18 7:38 ` 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-113374-4-rACRSr4zjP@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: link
Be 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).