diff options
Diffstat (limited to 'docs/ThreadSanitizer.rst')
| -rw-r--r-- | docs/ThreadSanitizer.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/ThreadSanitizer.rst b/docs/ThreadSanitizer.rst index cfb0a952e12e0..cfbaa63d64328 100644 --- a/docs/ThreadSanitizer.rst +++ b/docs/ThreadSanitizer.rst @@ -83,11 +83,11 @@ this purpose. # endif #endif -``__attribute__((no_sanitize_thread))`` +``__attribute__((no_sanitize("thread")))`` ----------------------------------------------- Some code should not be instrumented by ThreadSanitizer. One may use the -function attribute `no_sanitize_thread` to disable instrumentation of plain +function attribute ``no_sanitize("thread")`` to disable instrumentation of plain (non-atomic) loads/stores in a particular function. ThreadSanitizer still instruments such functions to avoid false positives and provide meaningful stack traces. This attribute may not be supported by other compilers, so we suggest @@ -99,9 +99,9 @@ Blacklist ThreadSanitizer supports ``src`` and ``fun`` entity types in :doc:`SanitizerSpecialCaseList`, that can be used to suppress data race reports in the specified source files or functions. Unlike functions marked with -`no_sanitize_thread` attribute, blacklisted functions are not instrumented at -all. This can lead to false positives due to missed synchronization via atomic -operations and missed stack frames in reports. +``no_sanitize("thread")`` attribute, blacklisted functions are not instrumented +at all. This can lead to false positives due to missed synchronization via +atomic operations and missed stack frames in reports. Limitations ----------- |