public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub 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: Mon, 14 Nov 2022 17:42:31 +0000 [thread overview] Message-ID: <bug-107678-4-dBq5fHm0gj@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 #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Perhaps some previously latent buffer overflow? I'm aware of e.g. __builtin_init_dwarf_reg_size_table theoretical problem with SVE, the builtin computes register sizes in 8-bit unsigned integers, but SVE can have 256-byte values.
next prev parent reply other threads:[~2022-11-14 17:42 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 [this message] 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-dBq5fHm0gj@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: linkBe 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).