public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ashimida at linux dot alibaba.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/102768] New: [feature request] Add support for aarch64 shadow call stack Date: Fri, 15 Oct 2021 09:17:58 +0000 [thread overview] Message-ID: <bug-102768-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102768 Bug ID: 102768 Summary: [feature request] Add support for aarch64 shadow call stack Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: ashimida at linux dot alibaba.com Target Milestone: --- Shadow Call Stack can be used to protect the return address of a function at runtime, and clang already supports this feature[1]. Linux kernel also recently had a submission to support Shadow Call Stack on aarch64 through a gcc plugin[2]. Could we add similar support in gcc? [1] https://clang.llvm.org/docs/ShadowCallStack.html [2] https://patchwork.kernel.org/project/linux-hardening/patch/1634167668-60198-1-git-send-email-ashimida@linux.alibaba.com/
next reply other threads:[~2021-10-15 9:17 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 9:17 ashimida at linux dot alibaba.com [this message] 2021-10-15 10:36 ` [Bug target/102768] " pinskia at gcc dot gnu.org 2021-10-15 15:59 ` nsz at gcc dot gnu.org 2021-10-15 17:08 ` ashimida at linux dot alibaba.com 2021-10-18 16:59 ` nsz at gcc dot gnu.org 2021-11-02 7:08 ` [Bug target/102768] [feature request] Add compiler " ashimida at linux dot alibaba.com 2021-11-23 8:12 ` ashimida at linux dot alibaba.com 2021-11-26 7:10 ` ashimida at linux dot alibaba.com 2021-12-06 2:49 ` ashimida at linux dot alibaba.com 2021-12-20 8:37 ` ashimida at linux dot alibaba.com 2022-02-22 12:43 ` nsz 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-102768-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).