From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E90DF3858C83; Mon, 6 Feb 2023 10:22:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E90DF3858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675678947; bh=Y6EE78wVCyz1k1rOXpV9AaCrFC7WkQrZQuVnDc/vHD8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Jh2eLawxN5uKvjD9rKa45g7XUR4Y7+xZboe/wVdJNj93Kwitcn28Qz7Y9+h5OvPgw MhgMV9MkLo3kuydne1tc0RQ0zajBCuj7qDiztHV8UGHiOdVw64M5WOSmkV9R102c+G 10pWnyiafD6rAQw09eTUf3NlCxVjw1lbJ+sqBdMs= From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/108656] [12/13 Regression] '-fcompare-debug' failure (length) w/ -O2 -fno-ipa-pure-const -fno-tree-dce --param early-inlining-insns=0 since r12-5236 Date: Mon, 06 Feb 2023 10:22:27 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: compare-debug-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108656 --- Comment #11 from rguenther at suse dot de --- On Mon, 6 Feb 2023, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108656 >=20 > --- Comment #10 from Jakub Jelinek --- > Anyway, if we decided that it is ok to have just the incoming ab edges, w= e'd > need to change any code that can DCE or inline calls to update abnormal e= dges > not just for the case where the last stmt used to be can_make_abnormal_go= to and > no longer is, but also for the case when the first stmt was returns_twice= call > and no longer is, in that case we'd need to drop that abnormal edge point= ing to > the start of the bb from the .ABNORMAL_DISPATCHER block. Doesn't cleanup CFG do this via removal of the unreachable=20 .ABNORMAL_DISPATCHER?=