public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6612] Docs: Clean up description of asan-kernel-mem-intrinsic-prefix.
Date: Sun, 12 Mar 2023 03:46:37 +0000 (GMT)	[thread overview]
Message-ID: <20230312034637.5125E3858D1E@sourceware.org> (raw)

https://gcc.gnu.org/g:f56ed5b3bcb9d94c0169d56b8bf652c7b5aa9fd3

commit r13-6612-gf56ed5b3bcb9d94c0169d56b8bf652c7b5aa9fd3
Author: Sandra Loosemore <sandra@codesourcery.com>
Date:   Sun Mar 12 03:41:11 2023 +0000

    Docs: Clean up description of asan-kernel-mem-intrinsic-prefix.
    
    gcc/ChangeLog:
            * doc/invoke.texi (Optimize Options):  Add markup to
            description of asan-kernel-mem-intrinsic-prefix, and clarify
            wording slightly.

Diff:
---
 gcc/doc/invoke.texi | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 3a6a97862b0..8d71d3d6ea5 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -15871,8 +15871,10 @@ E.g. to disable inline code use
 @option{--param asan-instrumentation-with-call-threshold=0}.
 
 @item asan-kernel-mem-intrinsic-prefix
-Prefix calls to memcpy, memset and memmove with __asan_ or __hwasan_
-for -fsanitize=kernel-address or -fsanitize=kernel-hwaddress.
+If nonzero, prefix calls to @code{memcpy}, @code{memset} and @code{memmove}
+with @samp{__asan_} or @samp{__hwasan_}
+for @option{-fsanitize=kernel-address} or @samp{-fsanitize=kernel-hwaddress},
+respectively.
 
 @item hwasan-instrument-stack
 Enable hwasan instrumentation of statically sized stack-allocated variables.

                 reply	other threads:[~2023-03-12  3:46 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=20230312034637.5125E3858D1E@sourceware.org \
    --to=sandra@gcc.gnu.org \
    --cc=gcc-cvs@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: 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).