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.
