| /llvm-project-15.0.7/clang/lib/Analysis/ |
| H A D | CFGReachabilityAnalysis.cpp | 24 : analyzed(cfg.getNumBlockIDs(), false) {} in CFGReverseBlockReachabilityAnalysis() 31 if (!analyzed[DstBlockID]) { in isReachable() 33 analyzed[DstBlockID] = true; in isReachable() 44 llvm::BitVector visited(analyzed.size()); in mapReachability() 47 DstReachability.resize(analyzed.size(), false); in mapReachability()
|
| /llvm-project-15.0.7/mlir/test/Transforms/ |
| H A D | test-inlining.mlir | 21 // test.region is analyzed recursively, so it must not have an invalid op. 38 // test.functional_region_op is not analyzed recursively, so it may have an
|
| /llvm-project-15.0.7/clang/include/clang/Analysis/Analyses/ |
| H A D | CFGReachabilityAnalysis.h | 35 ReachableSet analyzed; variable
|
| /llvm-project-15.0.7/llvm/test/Transforms/Attributor/ |
| H A D | alwaysinline.ll | 11 ; so the function can be analyzed 42 ; so it will not be analyzed 73 ; so it will not be analyzed
|
| /llvm-project-15.0.7/clang/test/Analysis/ |
| H A D | objc-method-coverage.m | 16 // CHECK: 2 AnalysisConsumer - The # of functions and blocks analyzed (as top level with inlining t…
|
| H A D | analyze-function-guide.m | 8 // CHECK-MISSING: Pass the -analyzer-display-progress for tracking which functions are analyzed.
|
| H A D | analyzeOneFunction.m | 41 … = [[NSString alloc] initWithFormat:@"test %f", 0.0]; // No warning: this function is not analyzed.
|
| H A D | mig.mm | 177 // The block is written within a function so that it was actually analyzed as 179 // variable of block type instead, it would not have been analyzed, because 182 // it will be analyzed as an inlined function rather than as a top-level
|
| /llvm-project-15.0.7/clang/test/Analysis/inlining/ |
| H A D | assume-super-init-does-not-return-nil.m | 29 // Test that this is being analyzed.
|
| /llvm-project-15.0.7/clang/docs/analyzer/developer-docs/ |
| H A D | DebugChecks.rst | 25 function being analyzed. 31 top-level function being analyzed. 34 top-level function being analyzed. 38 are several functions analyzed, display one graph per function. Beware 112 also be analyzed as a top-level function (in which case both TRUE and FALSE
|
| H A D | nullability.rst | 52 * We can either take the branch; this way the branch is analyzed 86 …alse positives but the functions that takes nullable parameters will be analyzed separately as wel…
|
| /llvm-project-15.0.7/llvm/test/Analysis/LoopAccessAnalysis/ |
| H A D | wrapping-pointer-versioning.ll | 28 ; The expression for %mul_ext as analyzed by SCEV is 95 ; The expression for %mul_ext as analyzed by SCEV is 146 ; The expression for %mul_ext as analyzed by SCEV is 193 ; The expression for %mul_ext as analyzed by SCEV is
|
| H A D | depend_diff_types_opaque_ptr.ll | 72 ; equivalent. This is a negative test to ensure that they are not analyzed as 114 ; are not analyzed as in the tests above.
|
| H A D | depend_diff_types.ll | 75 ; equivalent. This is a negative test to ensure that they are not analyzed as 119 ; are not analyzed as in the tests above.
|
| /llvm-project-15.0.7/llvm/test/Analysis/ValueTracking/ |
| H A D | select-pattern.ll | 5 ; as an operand to be analyzed. This would then cause
|
| /llvm-project-15.0.7/llvm/test/Transforms/LICM/ |
| H A D | AliasSetMemSet.ll | 2 ; Check no assertion when loop-idiom deletes the MemSet already analyzed by licm
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/misc/ |
| H A D | const-correctness.rst | 42 // The similar semantics of pointers are not (yet) analyzed. 64 Pointees can not be analyzed for constness yet. The following code shows this limitation.
|
| /llvm-project-15.0.7/polly/test/ScopInfo/ |
| H A D | multidim_fold_constant_dim_zero.ll | 8 ; output to undertand that the scop has been analyzed, but has also been
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/modernize/ |
| H A D | deprecated-headers.rst | 79 analyzed C++ source file is not included by any other C source files.
|
| /llvm-project-15.0.7/llvm/test/Transforms/LoopVectorize/ |
| H A D | vect.stats.ll | 8 ; CHECK: 2 loop-vectorize - Number of loops analyzed for vectorization
|
| /llvm-project-15.0.7/clang/lib/StaticAnalyzer/ |
| H A D | README.txt | 55 the behavior of the analyzed program from the entry point. To 115 The second prints to the console what function is being analyzed. The
|
| /llvm-project-15.0.7/llvm/test/Transforms/LoopVectorize/X86/ |
| H A D | vect.omp.force.ll | 8 ; CHECK: 2 loop-vectorize - Number of loops analyzed for vectorization
|
| /llvm-project-15.0.7/llvm/test/CodeGen/X86/ |
| H A D | win-alloca-expander.ll | 115 ; Test that the blocks are analyzed in the correct order.
|
| /llvm-project-15.0.7/clang/include/clang/StaticAnalyzer/Core/ |
| H A D | AnalyzerOptions.def | 339 "Whether the analyzed application runs in a controlled environment. " 348 "won't be analyzed.", 354 "flex\" won't be analyzed.",
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/bugprone/ |
| H A D | not-null-terminated-result.rst | 64 - If the new function is could be safe version and C++ files are analyzed and
|