[clang] [rtsan][NFC] Add 'known to have non-deterministic' caveat to documentation (PR #114281)
via cfe-commits
cfe-commits at lists.llvm.org
Wed Oct 30 10:53:10 PDT 2024
llvmbot wrote:
<!--LLVM PR SUMMARY COMMENT-->
@llvm/pr-subscribers-clang
Author: Chris Apple (cjappl)
<details>
<summary>Changes</summary>
As suggested by @<!-- -->fmayer in #<!-- -->113979
---
Full diff: https://github.com/llvm/llvm-project/pull/114281.diff
1 Files Affected:
- (modified) clang/docs/RealtimeSanitizer.rst (+2-2)
``````````diff
diff --git a/clang/docs/RealtimeSanitizer.rst b/clang/docs/RealtimeSanitizer.rst
index e5f5abfcd9b47e..193f5217c1a1a1 100644
--- a/clang/docs/RealtimeSanitizer.rst
+++ b/clang/docs/RealtimeSanitizer.rst
@@ -12,9 +12,9 @@ projects. RTSan can be used to detect real-time violations, i.e. calls to method
that are not safe for use in functions with deterministic run time requirements.
RTSan considers any function marked with the ``[[clang::nonblocking]]`` attribute
to be a real-time function. At run-time, if RTSan detects a call to ``malloc``,
-``free``, ``pthread_mutex_lock``, or anything else that could have a
+``free``, ``pthread_mutex_lock``, or anything else known to have a
non-deterministic execution time in a function marked ``[[clang::nonblocking]]``
-RTSan raises an error.
+it raises an error.
RTSan performs its analysis at run-time but shares the ``[[clang::nonblocking]]``
attribute with the :doc:`FunctionEffectAnalysis` system, which operates at
``````````
</details>
https://github.com/llvm/llvm-project/pull/114281
More information about the cfe-commits
mailing list