| /llvm-project-15.0.7/compiler-rt/test/tsan/Darwin/ |
| H A D | ignore-noninstrumented.mm | 2 // system libraries on OS X. There are currently false positives coming from
8 // Check that without the flag, there are false positives.
|
| /llvm-project-15.0.7/clang-tools-extra/test/clang-tidy/checkers/bugprone/ |
| H A D | multiple-statement-macro.cpp | 35 void positives() { in positives() function
|
| /llvm-project-15.0.7/clang/docs/ |
| H A D | ThreadSanitizer.rst | 99 instruments such functions to avoid false positives and provide meaningful stack
108 positives and incorrect stack traces. Therefore, it should be used with care,
120 at all. This can lead to false positives due to missed synchronization via
|
| H A D | MemorySanitizer.rst | 85 avoid false positives. This attribute may not be supported by other compilers,
93 positives and therefore should be used with care, and only if absolutely
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/modernize/ |
| H A D | use-equals-delete.rst | 7 To avoid false-positives, this check only applies in a translation unit that has
|
| H A D | deprecated-headers.rst | 80 Hence, to omit false-positives and wrong fixit-hints, we ignore emitting
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/bugprone/ |
| H A D | string-integer-assignment.rst | 32 In order to suppress false positives, use an explicit cast.
|
| H A D | unhandled-self-assignment.rst | 14 to avoid false positives. In case of a pointer or a C array, it's likely that self-copy
|
| /llvm-project-15.0.7/llvm/utils/valgrind/ |
| H A D | i386-pc-linux-gnu.supp | 9 # Python false positives according to
|
| H A D | x86_64-pc-linux-gnu.supp | 8 # Python false positives according to
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines/ |
| H A D | pro-type-member-init.rst | 19 account but generates false positives for fields initialized in
|
| H A D | owning-memory.rst | 113 code base might lead to false positives.
|
| /llvm-project-15.0.7/clang/test/SemaObjC/ |
| H A D | arc-peformselector.m | 40 // variations because it produces too many false positives.
|
| /llvm-project-15.0.7/clang/test/Analysis/ |
| H A D | localization.m | 162 …rent IfStmt must match the isCheckingPlurality confition to avoid false positives generated from c…
177 // False positives that we are not accounting for involve matching the heuristic
|
| H A D | delegates.m | 87 // involving [NSObject performSelector...] tend to lead to false positives.
|
| H A D | retain-release-region-store.m | 123 // This is a temporary hack to reduce false positives.
|
| /llvm-project-15.0.7/clang-tools-extra/docs/ |
| H A D | ReleaseNotes.rst | 201 - Fixed some false positives in :doc:`bugprone-infinite-loop
245 - Fixed false positives in :doc:`misc-redundant-expression
258 - Fixed false positives in :doc:`misc-unused-using-decls
|
| /llvm-project-15.0.7/third-party/benchmark/ |
| H A D | CMakeLists.txt | 26 # PGC++ maybe reporting false positives.
213 …if (NOT CMAKE_CXX_COMPILER_ID STREQUAL "Intel") #ICC17u2: Many false positives for Wstrict-aliasing
|
| /llvm-project-15.0.7/clang/docs/analyzer/developer-docs/ |
| H A D | IPA.rst | 69 of false positives, either by considering paths that the caller considers
86 enough that our tolerance for false positives is even lower here. A false
328 performance hit and the possibility of false positives on the path where the
|
| H A D | InitializerLists.rst | 14 I've seen a few false positives that appear because we construct
48 positives: when the list escapes, our ``RegionStoreManager`` is not magically
55 thing to do anyway) such checker would be able to solve the false positives by
|
| H A D | nullability.rst | 86 …y of the same symbol). So the symbol will remain nonnull to avoid false positives but the function…
|
| /llvm-project-15.0.7/clang/include/clang/StaticAnalyzer/Checkers/ |
| H A D | CheckerBase.td | 34 /// Released entries are stable, produce minimal, if any false positives,
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/ |
| H A D | Contributing.rst | 396 positives, but given that matching against an AST is not control- or data flow-
397 sensitive, a number of false positives are expected. The higher the false
399 Mechanisms should be put in place to help the user manage false positives.
400 - There are two primary mechanisms for managing false positives: supporting a
|
| /llvm-project-15.0.7/llvm/cmake/ |
| H A D | config-ix.cmake | 217 # party code may call MSan interceptors like strlen, leading to false positives.
431 # false positives.
|
| /llvm-project-15.0.7/utils/bazel/ |
| H A D | .bazelrc | 66 # Disable GCC warnings that are noisy and/or false positives on LLVM code.
|