From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org, gerald@pfeifer.com, richard.sandiford@arm.com
Subject: Re: [PATCH] wwwdocs: Document ShadowCallStack support
Date: Tue, 22 Feb 2022 11:26:24 +0100 [thread overview]
Message-ID: <YhS6UFxMHgX+7HzB@tucnak> (raw)
In-Reply-To: <mpto82zgqit.fsf@arm.com>
On Tue, Feb 22, 2022 at 10:11:06AM +0000, Richard Sandiford via Gcc-patches wrote:
> Document ShadowCallStack support. The option link doesn't work yet
> of course, but I checked that it works with gcc-12.1.0/ removed.
>
> OK to install?
>
> Thanks,
> Richard
>
>
> ---
> htdocs/gcc-12/changes.html | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
> index b6341fda..216ee0b6 100644
> --- a/htdocs/gcc-12/changes.html
> +++ b/htdocs/gcc-12/changes.html
> @@ -96,6 +96,17 @@ a work-in-progress.</p>
> Note that default vectorizer cost model has been changed which used to behave
> as <code>-fvect-cost-model=cheap</code> were specified.
> </li>
> + <li>
> + GCC now supports the
> + <a href="https://clang.llvm.org/docs/ShadowCallStack.html">
> + ShadowCallStack</a> sanitizer, which can be enabled using the
> + command-line option
> + <a href="https://gcc.gnu.org/onlinedocs/gcc-12.1.0/gcc/Instrumentation-Options.html#index-fsanitize_003dshadow-call-stack">
> + <code>-fshadow-call-stack</code></a>. This sanitizer currently
The option is -fsanitize=shadow-call-stack , no?
> + only works on AArch64 targets and it requires an environment in
> + which all code has been compiled with <code>-ffixed-r18</code>.
> + Its primary initial user is the Linux kernel.
> + </li>
> </ul>
>
Jakub
next prev parent reply other threads:[~2022-02-22 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 10:11 Richard Sandiford
2022-02-22 10:26 ` Jakub Jelinek [this message]
2022-02-22 10:52 ` Richard Sandiford
2022-02-23 6:31 ` Gerald Pfeifer
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=YhS6UFxMHgX+7HzB@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=richard.sandiford@arm.com \
/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: link
Be 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).