From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DD1A438357A6; Mon, 14 Nov 2022 17:45:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DD1A438357A6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1668447903; bh=QKRuK/uz4CRB5ZbA1AA8B9Km0QO/kaZoLtRs4cdDn+k=; h=From:To:Subject:Date:In-Reply-To:References:From; b=K3/hYclMv7j0fKXP9z19tMEOVH26Oy5QOzo0mFAFAhjH9JQnoKI/iOlYvun9GuZDN /k86NUIS5E+5V5YxFCRpb3VlF0pitHwZoquusc+TaLAwiTvFgwzN5p1cTmjm60w+tR eCdJYPp0/hdoO0E/0+KaAfSQA9lA0sAwtRdqQaZE= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107678] [13 Regression] Segfault in aarch64_fallback_frame_state when running SVE code Date: Mon, 14 Nov 2022 17:45:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: EH, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 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=3D107678 --- Comment #4 from Andrew Pinski --- Note aarch64_fallback_frame_state segfault is=20 if (pc[0] !=3D MOVZ_X8_8B || pc[1] !=3D SVC_0) pc comes from: unsigned *pc =3D context->ra; >so the size of the vectors could be a hint? It is not in this case. But it might be a hint on maybe the dwarf2 stack unwinding output is not fu= lly correct for non-constant offsets ...=