public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Marco Elver <melver@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. c890519eb128b23d9bc54356b2c95f64ff4ab01c
Date: Wed, 24 Jun 2020 08:51:04 +0000 (GMT)	[thread overview]
Message-ID: <20200624085105.015BD388A832@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  c890519eb128b23d9bc54356b2c95f64ff4ab01c (commit)
      from  2b70f89ff4df991b32d3680f56485470ec978bc6 (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 c890519eb128b23d9bc54356b2c95f64ff4ab01c
Author: Marco Elver <elver@google.com>
Date:   Fri Jun 19 14:23:08 2020 +0200

    gcc-11/changes: Document TSAN changes
    
    Document TSAN changes to support alternative runtimes, such as KCSAN.

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 9dba1e14..dc22f216 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -46,6 +46,21 @@ a work-in-progress.</p>
 <!-- .................................................................. -->
 <h2 id="general">General Improvements</h2>
 
+<ul>
+  <li>
+    <a href="https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual">
+    ThreadSanitizer</a> improvements to support alternative runtimes and
+    environments. The <a href="https://www.kernel.org/doc/html/latest/dev-tools/kcsan.html">
+    Linux Kernel Concurrency Sanitizer (KCSAN)</a> is now supported.
+    <ul>
+      <li>Add <code>--param tsan-distinguish-volatile</code> to optionally emit
+          instrumentation distinguishing volatile accesses.</li>
+      <li>Add <code>--param tsan-instrument-func-entry-exit</code> to optionally
+          control if function entries and exits should be instrumented.</li>
+    </ul>
+  </li>
+</ul>
+
 <!-- .................................................................. -->
 <h2 id="languages">New Languages and Language specific improvements</h2>
 

-----------------------------------------------------------------------

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-06-24  8:51 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=20200624085105.015BD388A832@sourceware.org \
    --to=melver@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: 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).