public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.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: Wed, 18 Jan 2023 12:36:54 +0000 [thread overview]
Message-ID: <bug-107678-4-8CyELqXn3P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107678-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107678
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Wilco Dijkstra <wilco@gcc.gnu.org>:
https://gcc.gnu.org/g:c98cd1df22fbe0829149e346a1ba9bf1f0be8a40
commit r13-5240-gc98cd1df22fbe0829149e346a1ba9bf1f0be8a40
Author: Wilco Dijkstra <wilco.dijkstra@arm.com>
Date: Tue Jan 3 15:57:46 2023 +0000
libgcc: Fix uninitialized RA signing on AArch64 [PR107678]
A recent change only initializes the regs.how[] during Dwarf unwinding
which resulted in an uninitialized offset used in return address signing
and random failures during unwinding. The fix is to encode the return
address signing state in REG_UNSAVED and a new state REG_UNSAVED_ARCHEXT.
libgcc/
PR target/107678
* unwind-dw2.h (REG_UNSAVED_ARCHEXT): Add new enum.
* unwind-dw2.c (uw_update_context_1): Add REG_UNSAVED_ARCHEXT case.
* unwind-dw2-execute_cfa.h: Use REG_UNSAVED_ARCHEXT/REG_UNSAVED to
encode the return address signing state.
* config/aarch64/aarch64-unwind.h (aarch64_demangle_return_addr)
Check current return address signing state.
(aarch64_frob_update_contex): Remove.
next prev parent reply other threads:[~2023-01-18 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 17:17 [Bug libgcc/107678] New: [13 Regression] Segfault in aarch64_fallback_frame_state avieira at gcc dot gnu.org
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 [this message]
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-8CyELqXn3P@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).