From: George Burgess IV Date: Tue, 26 Apr 2016 00:31:29 +0000 (+0000) Subject: [Docs] Fix indentation error introduced by r267447. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0865fe94e3c911db41319d1b73348f7732fa9126;p=clang [Docs] Fix indentation error introduced by r267447. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@267501 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/UndefinedBehaviorSanitizer.rst b/docs/UndefinedBehaviorSanitizer.rst index 1002729f05..db1325cc02 100644 --- a/docs/UndefinedBehaviorSanitizer.rst +++ b/docs/UndefinedBehaviorSanitizer.rst @@ -93,13 +93,13 @@ Available checks are: - ``-fsanitize=null``: Use of a null pointer or creation of a null reference. - ``-fsanitize=object-size``: An attempt to potentially use bytes which - the optimizer can determine are not part of the object being accessed. - This will also detect some types of undefined behavior that may not - directly access memory, but are provably incorrect given the size of - the objects involved, such as invalid downcasts and calling methods on - invalid pointers. These checks are made in terms of - ``__builtin_object_size``, and consequently may be able to detect more - problems at higher optimization levels. + the optimizer can determine are not part of the object being accessed. + This will also detect some types of undefined behavior that may not + directly access memory, but are provably incorrect given the size of + the objects involved, such as invalid downcasts and calling methods on + invalid pointers. These checks are made in terms of + ``__builtin_object_size``, and consequently may be able to detect more + problems at higher optimization levels. - ``-fsanitize=return``: In C++, reaching the end of a value-returning function without returning a value. - ``-fsanitize=returns-nonnull-attribute``: Returning null pointer