Searched refs:dataflow (Results 1 – 25 of 88) sorted by relevance
1234
34 using dataflow::UncheckedOptionalAccessDiagnoser;35 using dataflow::UncheckedOptionalAccessModel;42 using dataflow::ControlFlowContext; in analyzeFunction()43 using dataflow::DataflowAnalysisState; in analyzeFunction()51 dataflow::DataflowAnalysisContext AnalysisContext( in analyzeFunction()52 std::make_unique<dataflow::WatchedLiteralsSolver>()); in analyzeFunction()53 dataflow::Environment Env(AnalysisContext, FuncDecl); in analyzeFunction()59 BlockToOutputState = dataflow::runDataflowAnalysis( in analyzeFunction()
10 …: %no_fuzzer_cpp_compiler -c -fno-sanitize=all -fsanitize=dataflow %S/../../lib/fuzzer/dataflow/Da…11 …_compiler -c -fno-sanitize=all -fPIC %S/../../lib/fuzzer/dataflow/DataFlowCallbacks…12 DISABLED: %no_fuzzer_cpp_compiler -fno-sanitize=all -fsanitize=dataflow -fsanitize-coverage=trac…
4 # Disable, like other dataflow tests.9 RUN: %no_fuzzer_cpp_compiler -c -fno-sanitize=all -fsanitize=dataflow %S/../../lib/fuzzer/dataflow/…10 RUN: %no_fuzzer_cpp_compiler -c -fno-sanitize=all -fPIC %S/../../lib/fuzzer/dataflow…11 RUN: %no_fuzzer_cpp_compiler -fno-sanitize=all -fsanitize=dataflow -fsanitize-coverage=trace-pc-…12 RUN: %no_fuzzer_cpp_compiler -fno-sanitize=all -fsanitize=dataflow -fsanitize-coverage=trace-pc-…
30 namespace dataflow {40 typename _AnalysisDirTag = dataflow::forward_analysis_tag >69 bool isForwardAnalysis(dataflow::forward_analysis_tag) { return true; } in isForwardAnalysis()70 bool isForwardAnalysis(dataflow::backward_analysis_tag) { return false; } in isForwardAnalysis()
29 namespace dataflow {117 const clang::dataflow::MapLattice<Key, ElementLattice> &M) {130 const clang::dataflow::VarMapLattice<ElementLattice> &M) {
18 namespace dataflow {
22 namespace dataflow {
20 namespace dataflow {
21 namespace dataflow {
23 namespace dataflow {
27 namespace dataflow {
25 namespace dataflow {
32 namespace dataflow {
28 namespace dataflow { namespace157 auto StatusString = clang::dataflow::debugString(Result.getStatus()); in debugString()182 clang::dataflow::debugString(AtomAssignment.second)); in debugString()
25 namespace dataflow { namespace343 const Expr &clang::dataflow::ignoreCFGOmittedNodes(const Expr &E) { in ignoreCFGOmittedNodes()354 const Stmt &clang::dataflow::ignoreCFGOmittedNodes(const Stmt &S) { in ignoreCFGOmittedNodes()378 clang::dataflow::getObjectFields(QualType Type) { in getObjectFields()
24 namespace dataflow { namespace
3 Writing dataflow analyses in MLIR, or well any compiler, can often seem quite4 daunting and/or complex. A dataflow analysis generally involves propagating14 One type of dataflow analysis is a forward propagation analysis. This type of17 writing a simple forward dataflow analysis in MLIR. Let's say for this analysis67 held by an element of the lattice used by our dataflow analysis:181 The `ForwardDataFlowAnalysis` class represents the driver of the dataflow188 /// This class represents the main driver of the forward dataflow analysis. It
15 namespace dataflow { namespace