From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 07D8C3858C83; Wed, 19 Oct 2022 07:16:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 07D8C3858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666163794; bh=ArVIXSXlAVbQwAQPw6YMUYzAInm6fItmCwludPdkO/c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=baVXJrCphBRNKdKHVpBsIFUr6oyR4nFOLJB8ifsUyqIDHdaAAInzfadP3ZZ8Oexxs jJA4pVzmF9dRiBmk6ppU388oRS41+aK8sLe6lch98/Mfdg8PKMkMMJjiQ7+rnBoIOp MgZPEb5aH7JAwR/gnfYkOZ5TA6vjhDkBV3JCHm24= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107305] ICE: 'verify_gimple' failed Date: Wed, 19 Oct 2022 07:16:33 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: NEW 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: keywords blocked 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=3D107305 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |error-recovery, | |ice-on-invalid-code Blocks| |101057 --- Comment #4 from Richard Biener --- Yeah, the "design" of the GIMPLE frontend is that most IL validation is don= e by the verifiers instead of the parser. Maybe we can run the verifier on the parsing result and abort compilation if there was any error. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D101057 [Bug 101057] [gimplefe] GIMPLE frontend issues=