public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Matthew Malcomson <matmal01@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 05c170a452a9aecf36a719515a7e64f7999305e4 Date: Tue, 22 Dec 2020 14:53:35 +0000 (GMT) [thread overview] Message-ID: <20201222145335.11DF1383F867@sourceware.org> (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 05c170a452a9aecf36a719515a7e64f7999305e4 (commit) from fb048b7d45422cd869772462cba591a46f1b3b2f (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 05c170a452a9aecf36a719515a7e64f7999305e4 Author: Matthew Malcomson <matthew.malcomson@arm.com> Date: Tue Dec 22 13:24:15 2020 +0000 wwwdocs: Document new Hardware-assisted AddressSanitizer gcc-11/changes: Document new Hardware-assisted AddressSanitizer. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 1a9e72c1..d04b377d 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -116,6 +116,25 @@ a work-in-progress.</p> option (which defaults to 8 spaces per tab stop). </p> </li> + <li> + <p> + Introduce <a href="https://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html"> + Hardware-assisted AddressSanitizer</a> support. This sanitizer currently + only works for the AArch64 target. It helps debug address problems + similarly to + <a href="https://github.com/google/sanitizers/wiki/AddressSanitizer"> + AddressSanitizer</a> but is based on partial hardware assistance and + provides probabilistic protection to use less RAM at run time. + <a href="https://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html"> + Hardware-assisted AddressSanitizer</a> is not production-ready for user + space, and is provided mainly for use compiling the Linux Kernel. + </p> + To use this sanitizer the command line arguments are: + <ul> + <li><code>-fsanitize=hwaddress</code> to instrument userspace code.</li> + <li><code>-fsanitize=kernel-hwaddress</code> to instrument kernel code.</li> + </ul> + </li> </ul> <!-- .................................................................. --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-12-22 14:53 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: 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=20201222145335.11DF1383F867@sourceware.org \ --to=matmal01@sourceware.org \ --cc=gcc-cvs-wwwdocs@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).