public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "oconnor663 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110027] Misaligned vector store on detect_stack_use_after_return Date: Tue, 30 May 2023 14:49:52 +0000 [thread overview] Message-ID: <bug-110027-4-F6sVBG6aL7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110027-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110027 Jack O'Connor <oconnor663 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oconnor663 at gmail dot com --- Comment #3 from Jack O'Connor <oconnor663 at gmail dot com> --- Thanks to Andrew Pinski's comment about -fstack-protector-strong, I can now reproduce this issue on Godbolt: https://godbolt.org/z/47a695sWY. So the minimal set of flags to reproduce on most distros (other than Arch Linux) is: -mavx512f -fsanitize=address -fstack-protector-strong
next prev parent reply other threads:[~2023-05-30 14:49 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-29 20:18 [Bug sanitizer/110027] New: " sneves at dei dot uc.pt 2023-05-29 20:54 ` [Bug target/110027] " pinskia at gcc dot gnu.org 2023-05-30 8:06 ` rguenth at gcc dot gnu.org 2023-05-30 14:49 ` oconnor663 at gmail dot com [this message] 2023-10-22 18:06 ` gcc at sicherha dot de 2023-12-01 17:42 ` pinskia at gcc dot gnu.org 2023-12-01 17:46 ` pinskia at gcc dot gnu.org 2023-12-17 23:24 ` pinskia at gcc dot gnu.org 2024-03-08 4:13 ` pinskia at gcc dot gnu.org 2024-03-08 11:41 ` elrodc at gmail dot com 2024-03-08 18:10 ` gcc at sicherha dot de 2024-03-08 18:52 ` [Bug target/110027] [11/12/13/14 regression] " sjames at gcc dot gnu.org 2024-03-11 3:28 ` liuhongt at gcc dot gnu.org 2024-03-12 5:10 ` liuhongt at gcc dot gnu.org 2024-03-12 6:35 ` liuhongt at gcc dot gnu.org 2024-03-15 1:51 ` liuhongt at gcc dot gnu.org 2024-03-25 12:34 ` rguenth at gcc dot gnu.org 2024-04-08 15:43 ` xry111 at gcc dot gnu.org 2024-04-09 18:25 ` [Bug target/110027] [11/12/13/14 regression] Stack objects with extended alignments (vectors etc) misaligned " jakub at gcc dot gnu.org 2024-04-10 10:25 ` [Bug middle-end/110027] " jakub at gcc dot gnu.org 2024-04-11 6:53 ` liuhongt at gcc dot gnu.org 2024-04-11 8:16 ` jakub at gcc dot gnu.org 2024-04-11 9:14 ` cvs-commit at gcc dot gnu.org 2024-04-11 10:06 ` [Bug middle-end/110027] [11/12/13 " jakub at gcc dot gnu.org 2024-04-12 18:09 ` carlos.seo at linaro dot org 2024-04-21 4:09 ` cvs-commit at gcc dot gnu.org 2024-04-23 6:44 ` [Bug middle-end/110027] [11/12 " jakub 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-110027-4-F6sVBG6aL7@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).