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 010433856DC5; Wed, 14 Sep 2022 13:50:38 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 010433856DC5
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663163439;
	bh=vFPPGGmn+02yKa0lx5tsagr07lTH0YVFuXORRf3sedM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=RWpZ+nC009TuibcCRaGiKTdCzsJK7ecnVz3rydI6MJBeRQpxBOXSUSuBdrhnswo8/
	 iWm5b5efNrHS3TRx5Mdg/EK78gCn8WVd+RwWaUzXdaX9P+fBTdRJwqNPmwlGt3vgti
	 j9K4Bl6ns8NyVZUQua1uBmx6Vk2vv7Yz2rrrqbgI=
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106833] Miss to handle OPAQUE_TYPE specially in
 verify_type
Date: Wed, 14 Sep 2022 13:50:38 +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: ice-checking
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106833-4-Z9ZNbYzPII@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106833-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=3D106833

--- Comment #16 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #15)
> (In reply to Kewen Lin from comment #14)
> > Should be fixed on trunk
>=20
> I assume this is broken on the release branches too and we'll need backpo=
rts?

Good question, currently function verify_type uses are all guarded by
flag_checking, I just had a testing, the ICE didn't get exposed with release
branches, I think it is because that they are configured with
--enable-checking=3Drelease by default, but it's still reproducible with one
extra explicit option -fchecking=3D1 for release branches.

Hi Richi, what do you think of the backporting for this case?=