summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVedant Kumar <vsk@apple.com>2017-06-16 18:38:43 +0000
committerVedant Kumar <vsk@apple.com>2017-06-16 18:38:43 +0000
commite42e5cf8bd40cef5fce34eb9b2e26f7dac447078 (patch)
treefb36e57b03a1e319e27e9f1bf4d289bbce45d99e
parentc9fefaac676c33d4f3fa0acc061abbda9e0781e6 (diff)
downloadbcm5719-llvm-e42e5cf8bd40cef5fce34eb9b2e26f7dac447078.tar.gz
bcm5719-llvm-e42e5cf8bd40cef5fce34eb9b2e26f7dac447078.zip
[ubsan] docs: Add a note about pointers to volatile
llvm-svn: 305568
-rw-r--r--clang/docs/UndefinedBehaviorSanitizer.rst6
1 files changed, 6 insertions, 0 deletions
diff --git a/clang/docs/UndefinedBehaviorSanitizer.rst b/clang/docs/UndefinedBehaviorSanitizer.rst
index ea776a77047..85dd549baaf 100644
--- a/clang/docs/UndefinedBehaviorSanitizer.rst
+++ b/clang/docs/UndefinedBehaviorSanitizer.rst
@@ -148,6 +148,12 @@ You can also use the following check groups:
nullability does not have undefined behavior, it is often unintentional,
so UBSan offers to catch it.
+Volatile
+--------
+
+The ``null``, ``alignment``, ``object-size``, and ``vptr`` checks do not apply
+to pointers to types with the ``volatile`` qualifier.
+
Stack traces and report symbolization
=====================================
If you want UBSan to print symbolized stack trace for each error report, you
OpenPOWER on IntegriCloud