From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B68523858C66; Sun, 10 Mar 2024 03:46:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B68523858C66 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710042379; bh=AeKasHwGf0WBK7Qcf1KYwkdnTvy0X8U4ll/HroOcyrU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=bYWVi6TlEBRvPNHil/8UokTQjy9kq8QxBAdBSHy9Rk6fGQbri4M+yNQaQOz7IirJJ k00WPrIXnv4KNFWiOK42BeJltjSttRR42yetNcJuoanewitGkxbb6HHiDZY1UXbm9z Vi3SiIcFrc6pWf5DPCdRKCslBKLxytq2qM7SAvew= From: "law at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/110956] [13/14 regression] gcc_assert is hit at gcc-13.2.0/libgcc/unwind-dw2-fde.c#L291 with some special library Date: Sun, 10 Mar 2024 03:46:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Version: 13.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: law at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution cc 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=3D110956 Jeffrey A. Law changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED CC| |law at gcc dot gnu.org --- Comment #14 from Jeffrey A. Law --- I'd think the right thing to do is close this one and track in the newer bu= g.=20 It's not clear they're actually the same underlying problem, even though th= ey have the same failure signature.=