public inbox for
help / color / mirror / Atom feed
From: Richard Sandiford <>
Subject: gcc-wwwdocs branch master updated. 89d90f8c476d7980752ab43ec80cfa414996a7f0
Date: Fri, 25 Feb 2022 19:01:57 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  89d90f8c476d7980752ab43ec80cfa414996a7f0 (commit)
      from  c2db1d56d28f04ba1b023d6f5d48d7948e9079d8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 89d90f8c476d7980752ab43ec80cfa414996a7f0
Author: Richard Sandiford <>
Date:   Tue Feb 22 09:19:53 2022 +0000

    Document ShadowCallStack support

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 4be3ee72..e7c6ed8e 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>
+    GCC now supports the
+    <a href="">
+    ShadowCallStack</a> sanitizer, which can be enabled using the
+    command-line option
+    <a href="">
+    <code>-fsanitize=shadow-call-stack</code></a>.  This sanitizer currently
+    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>
 <!-- .................................................................. -->


Summary of changes:
 htdocs/gcc-12/changes.html | 11 +++++++++++
 1 file changed, 11 insertions(+)


                 reply	other threads:[~2022-02-25 19:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).