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 DA0E93858D28; Wed, 18 Jan 2023 21:30:41 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DA0E93858D28
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1674077441;
	bh=BYwNDusY5D2wBqShDo7WRYXta9yTEkX8G+W7f7Y3Tew=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=X6XQLSc+yiDV8+PAaiGYw8Or4ntB19vupZ1a4bohF6zhBvQs8Y2CF2IErnq2EcRxQ
	 3RQqpkUkG44BK40b6z6p3yY0NHpiMjJE8CqRKLUlz/0kv1WH44BUD3KKOcfRyoDmQn
	 i97qw/0xT1Tdcd34LN7050txyt5sSNdTbALQDeog=
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105469] [10/11/12/13 Regression] "execution reached
 an unreachable program point" with -flto since r5-7027-g0b986c6ac777aa4e
Date: Wed, 18 Jan 2023 21:30:41 +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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
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: 10.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-105469-4-PKCf8XtNgM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-105469-4@http.gcc.gnu.org/bugzilla/>
References: <bug-105469-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=3D105469

--- Comment #18 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
It should just make any bug to go latent.  It surprises me it makes any
difference given that things not cloned by ipa-cp should be all handled by
ipa-sra.=