From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 041143858416; Wed, 25 Oct 2023 20:27:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 041143858416 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698265634; bh=tXp2D0TN9oGkxdxPmG17anADXL3dPt7UXMVjFEBu6OQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=VdaKcr3WSfSvgmzSEVKpk1ouK1UEA7Qbux2CW40H5tJFNFG1NwnqgHwEgOLMX5jnc 3WAyamkdWy4AvJtFbI8+a9jPVWI24uzklX9upbcewVdN2lkQd87ulDJI447pyOX0iJ AWWVe0VAsbyEaEsIZfWCG1T8kMwfGyBPGPX2O59k= From: "ppalka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBjKysvMTAwMjkxXSBbMTEvMTIvMTMvMTQgUmVncmVzc2lv?= =?UTF-8?B?bl0gaW50ZXJuYWwgY29tcGlsZXIgZXJyb3I6IHRyeWluZyB0byBjYXB0dXJl?= =?UTF-8?B?IOKAmHRoaXPigJkgaW4gaW5zdGFudGlhdGlvbiBvZiBnZW5lcmljIGxhbWJk?= =?UTF-8?B?YQ==?= Date: Wed, 25 Oct 2023 20:27:13 +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: 11.0 X-Bugzilla-Keywords: ice-on-invalid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ppalka at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.5 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=3D100291 --- Comment #8 from Patrick Palka --- Maybe not exactly a dup, since this is an ICE-on-invalid testcase and stric= tly speaking a regression. But it doesn't seem like a regression worth fixing = in release branches. And the underlying cause is the same as in PR106086 so m= ight as well call it a dup.=