llvmorg-github-actions[bot] wrote:
<!--LLVM PR SUMMARY COMMENT--> @llvm/pr-subscribers-clang Author: Matthew Nagy (gbMattN) <details> <summary>Changes</summary> --- Full diff: https://github.com/llvm/llvm-project/pull/198331.diff 1 Files Affected: - (modified) clang/docs/TypeSanitizer.rst (+3-3) ``````````diff diff --git a/clang/docs/TypeSanitizer.rst b/clang/docs/TypeSanitizer.rst index 08cb247aefe3a..ce0aaaf62ac98 100644 --- a/clang/docs/TypeSanitizer.rst +++ b/clang/docs/TypeSanitizer.rst @@ -93,7 +93,7 @@ to print the full trace. To get nicer stack traces in error messages add ``-fno- } # Compile and link - % clang++ -g -fsanitize=type example_AliasViolation.cc + % clang++ -g -fsanitize=type example_AliasViolation.c The program will print an error message to ``stderr`` each time a strict aliasing violation is detected. The program won't terminate, which will allow you to detect many strict aliasing violations in one @@ -114,7 +114,7 @@ Error terminology ------------------ There are some terms that may appear in TypeSanitizer errors that are derived from -`TBAA Metadata <https://llvm.org/docs/LangRef.html#tbaa-metadata>`. This section hopes to provide a +`TBAA Metadata <https://llvm.org/docs/LangRef.html#tbaa-metadata>`_. This section hopes to provide a brief dictionary of these terms. * ``omnipotent char``: This is a special type which can alias with anything. Its name comes from the C/C++ @@ -207,7 +207,7 @@ Limitations does at least mean that TypeSanitizer will catch any aliasing violations that would cause bugs when compiling with Clang & LLVM. * TypeSanitizer cannot currently be run alongside other sanitizers such as - AddressSanitizer, ThreadSanitizer or UndefinedBehaviourSanitizer. + AddressSanitizer or ThreadSanitizer. Current Status -------------- `````````` </details> https://github.com/llvm/llvm-project/pull/198331 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
