From: Jakub Jelinek <jakub@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "Martin Liška" <mliska@suse.cz>, gcc <gcc@gcc.gnu.org>,
ro@gcc.gnu.org, "Martin Liška" <marxin@gcc.gnu.org>,
"Marco Elver" <elver@google.com>,
"Alexander Potapenko" <glider@google.com>
Subject: Re: New ThreadSanitizer runtime (v3)
Date: Mon, 22 Nov 2021 20:20:50 +0100 [thread overview]
Message-ID: <20211122192050.GQ2646553@tucnak> (raw)
In-Reply-To: <CACT4Y+YxdB9BnzGEgKuyv0uBA_cmfHMCw2JVfXojVDKeuR3Vvg@mail.gmail.com>
On Mon, Nov 22, 2021 at 08:00:38PM +0100, Dmitry Vyukov wrote:
> Not sure about gcc, but in clang the old no_sanitize_thread attribute
> disabled only part of instrumentation (only memory accesses, but not
> atomics and function entry/exit). The new attribute disables all
> instrumentation.
In gcc no_sanitize("thread") as well as no_sanitize_thread attributes
affect everything (function entry/exit, atomics and memory accesses).
Jakub
next prev parent reply other threads:[~2021-11-22 19:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 15:22 Dmitry Vyukov
2021-11-22 18:30 ` Martin Liška
2021-11-22 19:00 ` Dmitry Vyukov
2021-11-22 19:07 ` Martin Liška
2021-11-22 19:54 ` Marco Elver
2021-11-22 19:20 ` Jakub Jelinek [this message]
2021-11-22 18:38 ` Martin Liška
2021-11-22 19:01 ` Dmitry Vyukov
2021-11-29 18:16 ` Martin Liška
2021-11-30 4:17 ` Dmitry Vyukov
2021-12-23 12:10 ` Martin Liška
2021-12-23 12:21 ` Dmitry Vyukov
2021-11-23 13:49 ` Florian Weimer
2021-11-23 13:51 ` Dmitry Vyukov
2021-11-23 13:59 ` Florian Weimer
2021-11-23 15:37 ` Dmitry Vyukov
2021-11-23 16:16 ` Florian Weimer
2021-11-23 16:52 ` Dmitry Vyukov
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=20211122192050.GQ2646553@tucnak \
--to=jakub@redhat.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=gcc@gcc.gnu.org \
--cc=glider@google.com \
--cc=marxin@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=ro@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).