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 middle-end/112510] [11/12/13/14 Regression]: ASAN code injection breaks alignment of stack variables Date: Wed, 22 Nov 2023 16:20:31 +0000 [thread overview] Message-ID: <bug-112510-4-tRm5lakjyr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112510-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112510 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Can't reproduce, neither with GCC 12 nor current trunk. In the ASAN_OPTIONS=detect_stack_use_after_return=1 case, the stack frames are allocated by __asan_stack_malloc_4, but that seems to return enough aligned frames for me (eventhough the routine doesn't have an argument to request a particular alignment). Even tried struct __attribute__((aligned (64))) S { char buf[64]; }; __attribute__((noinline, noclone, noipa)) void bar (struct S *p, char *a) { if ((__UINTPTR_TYPE__)p % 64) __builtin_abort (); } __attribute__((noinline, noclone, noipa)) void foo (void) { struct S s; char a; bar (&s, &a); } int main () { for (int i = 0; i < 32; ++i) foo (); } and the frames were sufficiently aligned in all 32 cases.
next prev parent reply other threads:[~2023-11-22 16:20 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-13 12:04 [Bug c++/112510] New: Regression: " sadko4u at gmail dot com 2023-11-13 12:25 ` [Bug c++/112510] " rguenth at gcc dot gnu.org 2023-11-13 12:33 ` sadko4u at gmail dot com 2023-11-13 12:52 ` sadko4u at gmail dot com 2023-11-14 6:28 ` [Bug middle-end/112510] " pinskia at gcc dot gnu.org 2023-11-14 6:32 ` pinskia at gcc dot gnu.org 2023-11-14 7:55 ` sadko4u at gmail dot com 2023-11-14 8:02 ` sadko4u at gmail dot com 2023-11-14 8:05 ` [Bug middle-end/112510] [11/12/13/14 Regression]: " pinskia at gcc dot gnu.org 2023-11-14 8:13 ` rguenth at gcc dot gnu.org 2023-11-14 8:37 ` sadko4u at gmail dot com 2023-11-14 8:41 ` sadko4u at gmail dot com 2023-11-14 8:50 ` sadko4u at gmail dot com 2023-11-14 9:10 ` sadko4u at gmail dot com 2023-11-14 9:15 ` sadko4u at gmail dot com 2023-11-14 9:28 ` sadko4u at gmail dot com 2023-11-22 16:20 ` jakub at gcc dot gnu.org [this message] 2023-11-22 18:31 ` sadko4u at gmail dot com 2023-12-01 17:46 ` pinskia 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-112510-4-tRm5lakjyr@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).