# endif
#endif
-``__attribute__((no_sanitize_memory))``
+``__attribute__((no_sanitize("memory")))``
-----------------------------------------------
Some code should not be checked by MemorySanitizer. One may use the function
-attribute `no_sanitize_memory` to disable uninitialized checks in a particular
-function. MemorySanitizer may still instrument such functions to avoid false
-positives. This attribute may not be supported by other compilers, so we
-suggest to use it together with ``__has_feature(memory_sanitizer)``.
+attribute ``no_sanitize("memory")`` to disable uninitialized checks in a
+particular function. MemorySanitizer may still instrument such functions to
+avoid false positives. This attribute may not be supported by other compilers,
+so we suggest to use it together with ``__has_feature(memory_sanitizer)``.
Blacklist
---------
# 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
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
-----------