public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "avieira at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/107678] New: [13 Regression] Segfault in aarch64_fallback_frame_state
Date: Mon, 14 Nov 2022 17:17:07 +0000 [thread overview]
Message-ID: <bug-107678-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107678
Bug ID: 107678
Summary: [13 Regression] Segfault in
aarch64_fallback_frame_state
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcc
Assignee: unassigned at gcc dot gnu.org
Reporter: avieira at gcc dot gnu.org
Target Milestone: ---
Hi,
We ran into a segfault when running SPEC 2017 Parest for aarch64-none-linux-gnu
on a Neoverse V1 target after g:146e45914032
These are the relevant frames of the segfault:
#0 0x0000ffff8bd2dd04 in aarch64_fallback_frame_state (context=0xffffe11f6e10,
fs=0xffffe11f71d0)
at ./md-unwind-support.h:74
#1 uw_frame_state_for (context=context@entry=0xffffe11f6e10,
fs=fs@entry=0xffffe11f71d0)
at .../libgcc/unwind-dw2.c:1275
#2 0x0000ffff8bd2f0ec in _Unwind_RaiseException (exc=0x36b105d0)
at .../libgcc/unwind.inc:104
#3 0x0000ffff8be8d6b4 in __cxxabiv1::__cxa_throw (obj=<optimized out>,
tinfo=0x56bf58 <typeinfo for dealii::SolverControl::NoConvergence>,
dest=0x468c00 <dealii::SolverControl::NoConvergence::~NoConvergence()
[clone .lto_priv.0]>)
at .../libstdc++-v3/libsupc++/eh_throw.cc:93
We do not see the same failure for a NEON only run, so the size of the vectors
could be a hint? But I haven't confirmed this.
next reply other threads:[~2022-11-14 17:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 17:17 avieira at gcc dot gnu.org [this message]
2022-11-14 17:41 ` [Bug target/107678] [13 Regression] Segfault in aarch64_fallback_frame_state when running SVE code pinskia at gcc dot gnu.org
2022-11-14 17:42 ` jakub at gcc dot gnu.org
2022-11-14 17:43 ` jakub at gcc dot gnu.org
2022-11-14 17:45 ` pinskia at gcc dot gnu.org
2022-11-16 12:42 ` rguenth at gcc dot gnu.org
2022-11-21 10:06 ` marxin at gcc dot gnu.org
2022-12-01 14:46 ` wilco at gcc dot gnu.org
2022-12-01 16:52 ` wilco at gcc dot gnu.org
2022-12-03 21:24 ` laurent.alfonsi at linaro dot org
2022-12-20 15:40 ` rguenth at gcc dot gnu.org
2023-01-18 12:36 ` cvs-commit at gcc dot gnu.org
2023-01-23 16:46 ` wilco at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-107678-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).