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/111917] [11/12/13 Regression] ICE in as_a, at is-a.h:255 since GCC-7 Date: Fri, 10 Nov 2023 14:24:45 +0000 [thread overview] Message-ID: <bug-111917-4-9EXT0jkxkX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111917-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111917 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:28d9e033a8e95c024e27cb495db610aac37a0f88 commit r13-8045-g28d9e033a8e95c024e27cb495db610aac37a0f88 Author: Richard Biener <rguenther@suse.de> Date: Mon Oct 23 11:25:17 2023 +0200 tree-optimization/111917 - bougs IL after guard hoisting The unswitching code to hoist guards inserts conditions in wrong places. The following fixes this, simplifying code. PR tree-optimization/111917 * tree-ssa-loop-unswitch.cc (hoist_guard): Always insert new conditional after last stmt. * gcc.dg/torture/pr111917.c: New testcase. (cherry picked from commit d96bd4aade170fcd86f5f09b68b770dde798e631)
next prev parent reply other threads:[~2023-11-10 14:24 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-22 9:20 [Bug tree-optimization/111917] New: ICE in as_a, at is-a.h:255 since GCC-8 shaohua.li at inf dot ethz.ch 2023-10-22 11:05 ` [Bug tree-optimization/111917] [11/12/13/14 Regression] " tkoenig at gcc dot gnu.org 2023-10-22 16:30 ` pinskia at gcc dot gnu.org 2023-10-22 23:16 ` [Bug tree-optimization/111917] [11/12/13/14 Regression] ICE in as_a, at is-a.h:255 since GCC-7 pinskia at gcc dot gnu.org 2023-10-23 6:08 ` tkoenig at gcc dot gnu.org 2023-10-23 6:12 ` tkoenig at gcc dot gnu.org 2023-10-23 9:21 ` rguenth at gcc dot gnu.org 2023-10-23 10:35 ` cvs-commit at gcc dot gnu.org 2023-10-23 10:35 ` [Bug tree-optimization/111917] [11/12/13 " rguenth at gcc dot gnu.org 2023-11-10 14:24 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-27 13:10 ` [Bug tree-optimization/111917] [11/12 " cvs-commit at gcc dot gnu.org 2023-12-15 12:18 ` [Bug tree-optimization/111917] [11 " cvs-commit at gcc dot gnu.org 2023-12-15 12:23 ` 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-111917-4-9EXT0jkxkX@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).