From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 2A2A8385841A; Wed,  7 Sep 2022 13:32:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2A2A8385841A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1662557534;
	bh=FEyeMomaE6o4NACIsb99kAVIt7hzKnTLfGFrRzCSh50=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=QbQmhqCS394pzlwRvS0D5DQCj3602LoVHwMH/i4+TBLrC7o7DofrO7N9BiuSOYdUx
	 nYf0YwMVr0jWRVNMoTT7I4j4zD94A+TcGTS78bxCOsFlVYLKOqNJCReb1w6kC3r2HS
	 igk0x3BCv22pEQtPgk7VRK+x2rGPxd4KxG3vCrjc=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106870] ctrl_altering flag is not set correctly
Date: Wed, 07 Sep 2022 13:32:13 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106870-4-ZcFCMv4Tme@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106870-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
gcc.dg/torture/pr57036-2.c shows how inlining and non-local gotos come into
play here.

Note the flag was specifically invented to not make CFG verification ICE
when a function in the middle of a block becomes noreturn, for example
via IPA analysis.  It wasn't necessarily required to have the flag set
on stmts ending a BB.

Still not having the flag set prevents nothing to put stmts after such
call and we'd not complain.

gcc.dg/torture/pr83055.c shows how the checking is confused as called from
gimple_flow_call_edges_add after adding loads of fake edges.=