public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106288] New: stack protector fails to check stack canary for noreturn function Date: Wed, 13 Jul 2022 22:47:26 +0000 [thread overview] Message-ID: <bug-106288-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106288 Bug ID: 106288 Summary: stack protector fails to check stack canary for noreturn function Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com Target Milestone: --- [hjl@gnu-tgl-3 stack-protector]$ cat x.c extern void foo (void) __attribute__ ((noreturn)); void bar (void) { foo (); } [hjl@gnu-tgl-3 stack-protector]$ /export/build/gnu/tools-build/gcc-gitlab-debug/build-x86_64-linux/gcc/xgcc -B/export/build/gnu/tools-build/gcc-gitlab-debug/build-x86_64-linux/gcc/ -O2 -Wall -fstack-protector-all -S x.c [hjl@gnu-tgl-3 stack-protector]$ cat x.s .file "x.c" .text .p2align 4 .globl bar .type bar, @function bar: .LFB0: .cfi_startproc subq $24, %rsp .cfi_def_cfa_offset 32 movq %fs:40, %rax movq %rax, 8(%rsp) xorl %eax, %eax call foo .cfi_endproc .LFE0: .size bar, .-bar .ident "GCC: (GNU) 13.0.0 20220713 (experimental)" .section .note.GNU-stack,"",@progbits [hjl@gnu-tgl-3 stack-protector]$ There should be a stack canary check before calling foo since foo won't return.
next reply other threads:[~2022-07-13 22:47 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-13 22:47 hjl.tools at gmail dot com [this message] 2022-07-13 22:49 ` [Bug middle-end/106288] " 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-106288-4@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).