From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by sourceware.org (Postfix) with ESMTP id A1B4D3857809 for ; Tue, 22 Feb 2022 09:49:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A1B4D3857809 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5F6F31063; Tue, 22 Feb 2022 01:49:34 -0800 (PST) Received: from localhost (unknown [10.32.98.88]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C785C3F5A1; Tue, 22 Feb 2022 01:49:33 -0800 (PST) From: Richard Sandiford To: gcc-patches@gcc.gnu.org Mail-Followup-To: gcc-patches@gcc.gnu.org, gerald@pfeifer.com, richard.sandiford@arm.com Subject: Re: [PATCH 1/2] wwwdocs: Group sanitiser changes together References: Date: Tue, 22 Feb 2022 09:49:32 +0000 In-Reply-To: (Richard Sandiford's message of "Tue, 22 Feb 2022 09:45:44 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-12.4 required=5.0 tests=BAYES_00, GIT_PATCH_0, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2022 09:49:36 -0000 Richard Sandiford writes: > Group the ThreadSanitizer and HardwareAssistedAddressSanitizer > changes under a single top-level bullet point. This makes it > easier to add a third sanitiser-related change. > > No (intended) change to the actual text or wording. (TBH I don't > understand the ThreadSanitizer bit: is it describing three changes > (KCSAN + two new options), four changes (other environments), > or one big inter-related change?) > > OK to install? Err, scratch that. Clearly I've not had tea this morning, and forgot which version we're about to release :-) Richard > > Richard > > --- > htdocs/gcc-11/changes.html | 63 ++++++++++++++++++++++---------------- > 1 file changed, 36 insertions(+), 27 deletions(-) > > diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html > index 8e6d4ec8..cc3ae989 100644 > --- a/htdocs/gcc-11/changes.html > +++ b/htdocs/gcc-11/changes.html > @@ -69,18 +69,6 @@ You may also want to check out our >

General Improvements

> >
    > -
  • > - > - ThreadSanitizer improvements to support alternative runtimes and > - environments. The > - Linux Kernel Concurrency Sanitizer (KCSAN) is now supported. > -
      > -
    • Add --param tsan-distinguish-volatile to optionally emit > - instrumentation distinguishing volatile accesses.
      • > -
    • Add --param tsan-instrument-func-entry-exit to optionally > - control if function entries and exits should be instrumented.
      • > -
    > -
    • >
  • >

    > In previous releases of GCC, the "column numbers" emitted in diagnostics > @@ -121,22 +109,43 @@ You may also want to check out our >

    >
    • >
  • > -

    > - Introduce > - Hardware-assisted AddressSanitizer support. This sanitizer currently > - only works for the AArch64 target. It helps debug address problems > - similarly to > - > - AddressSanitizer but is based on partial hardware assistance and > - provides probabilistic protection to use less RAM at run time. > - > - Hardware-assisted AddressSanitizer is not production-ready for user > - space, and is provided mainly for use compiling the Linux Kernel. > -

    > - To use this sanitizer the command line arguments are: > + Sanitizer improvements: >
      > -
    • -fsanitize=hwaddress to instrument userspace code.
      • > -
    • -fsanitize=kernel-hwaddress to instrument kernel code.
      • > +
    • > + > + ThreadSanitizer improvements to support alternative runtimes > + and environments. The > + > + Linux Kernel Concurrency Sanitizer (KCSAN) is now supported. > +
        > +
      • Add --param tsan-distinguish-volatile to optionally > + emit instrumentation distinguishing volatile accesses.
        • > +
      • Add --param tsan-instrument-func-entry-exit to > + optionally control if function entries and exits should be > + instrumented.
        • > +
      > +
      • > +
    • > +

      > + Introduce > + Hardware-assisted AddressSanitizer support. This sanitizer currently > + only works for the AArch64 target. It helps debug address problems > + similarly to > + > + AddressSanitizer but is based on partial hardware assistance and > + provides probabilistic protection to use less RAM at run time. > + > + Hardware-assisted AddressSanitizer is not production-ready for user > + space, and is provided mainly for use compiling the Linux Kernel. > +

      > +

      > + To use this sanitizer the command line arguments are: > +

        > +
      • -fsanitize=hwaddress to instrument userspace code.
        • > +
      • -fsanitize=kernel-hwaddress to instrument kernel code.
        • > +
      > +

      > +
      • >
    >
    • >