From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E6C9C3858D35; Mon, 27 May 2024 07:10:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E6C9C3858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1716793801; bh=bIlkaHXCvZceve1+sXgdgQbPFQAXKksMB/VW0Xtx3AA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Twv3TdbxqeFg9eGYGRk5yRjL8fi5QQcc5BgN55NMObry4GipfbglurLaRuZWcPJbN i5hDRrSClibzM2DX17Otno7VnjyhAbA6TjTYbBd3jxBO0l1ESaQLsEvOoj13N2HSv4 kom2BlfDuf3C0YzhPqpdO/Rc6AhFmlnwSioVGWD4= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115232] [14/15 regression] ICE during GIMPLE pass during waccess Date: Mon, 27 May 2024 07:10:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 14.1.1 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to 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=3D115232 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot = gnu.org --- Comment #3 from Richard Biener --- (gdb) p newc $1 =3D (const demangle_component &) (gdb) p delc $2 =3D (const demangle_component &) 1763 demangle_component *ndc =3D cplus_demangle_v3_components (new_str= , 0, &np); 1764 demangle_component *ddc =3D cplus_demangle_v3_components (del_str= , 0, &dp); 1765 bool mismatch =3D new_delete_mismatch_p (*ndc, *ddc); (gdb) p new_str $3 =3D 0x7ffff7009ea8 "_ZZN5OuterIvE6methodIvEEvvQ3cstITL0__EEN5InnernwEm" (gdb) p del_str $4 =3D 0x7ffff7009e70 "_ZZN5OuterIvE6methodIvEEvvQ3cstITL0__EEN5InnerdlEPv" so we cannot demangle these? But we expect no failure. It should be trivi= al to build in safety here, mine for that. I'll keep the PR open for the failed demangle though.=