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/107876] [13 Regression] ICE in verify_dominators, at dominance.cc:1184 (error: dominator of 4 should be 14, not 16) since r13-3749-g7314b98b1bcd382c
Date: Mon, 28 Nov 2022 09:05:21 +0000	[thread overview]
Message-ID: <bug-107876-4-tstCAsnyvP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107876-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107876

--- Comment #5 from CVS 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:238cf114de16518c6569f0cdd2c4d6211ac98a74

commit r13-4317-g238cf114de16518c6569f0cdd2c4d6211ac98a74
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Nov 28 09:19:33 2022 +0100

    tree-optimization/107876 - unswitching of switch

    The following shows a missed update of dominators when unswitching
    removes unreachable edges from switch stmts it unswitches.  Fixed
    by wiping dominator info in that case.

            PR tree-optimization/107876
            * tree-ssa-loop-unswitch.cc (clean_up_after_unswitching): Wipe
            dominator info if we removed an edge.

            * g++.dg/tree-ssa/pr107876.C: New testcase.

  parent reply	other threads:[~2022-11-28  9:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26  8:18 [Bug tree-optimization/107876] New: [13 Regression] ICE in verify_dominators, at dominance.cc:1184 (error: dominator of 4 should be 14, not 16) asolokha at gmx dot com
2022-11-26 17:46 ` [Bug tree-optimization/107876] " pinskia at gcc dot gnu.org
2022-11-26 17:48 ` pinskia at gcc dot gnu.org
2022-11-28  6:48 ` [Bug tree-optimization/107876] [13 Regression] ICE in verify_dominators, at dominance.cc:1184 (error: dominator of 4 should be 14, not 16) since r13-3749-g7314b98b1bcd382c marxin at gcc dot gnu.org
2022-11-28  7:36 ` rguenth at gcc dot gnu.org
2022-11-28  8:13 ` rguenth at gcc dot gnu.org
2022-11-28  9:05 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-28  9:05 ` rguenth at gcc dot gnu.org
2023-08-19  9:27 ` fxcoudert at gcc dot gnu.org
2023-09-01 21:43 ` egallager at gcc dot gnu.org
2023-09-12  7:12 ` 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-107876-4-tstCAsnyvP@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).