On Fri, 19 Jun 2020 at 14:25, Marco Elver <el...@google.com> wrote: > > Document TSAN changes to support alternative runtimes, such as KCSAN.
Is this one good to go, or any objections? Thanks, -- Marco > --- > htdocs/gcc-11/changes.html | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > 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> > > -- > 2.27.0.111.gc72c7da667-goog >
