Home
last modified time | relevance | path

Searched refs:flow (Results 1 – 25 of 436) sorted by relevance

12345678910>>...18

/llvm-project/polly/lib/External/isl/
H A Disl_flow.c987 __isl_take isl_flow *flow) in handle_coscheduled() argument
992 return flow; in handle_coscheduled()
1008 return isl_flow_free(flow); in handle_coscheduled()
1030 return isl_flow_free(flow); in handle_coscheduled()
1039 flow->dep[pos].map = isl_map_union(flow->dep[pos].map, in handle_coscheduled()
1048 return flow; in handle_coscheduled()
2101 isl_ctx *isl_union_flow_get_ctx(__isl_keep isl_union_flow *flow) in isl_union_flow_get_ctx() argument
2103 return flow ? isl_union_map_get_ctx(flow->must_dep) : NULL; in isl_union_flow_get_ctx()
2108 __isl_null isl_union_flow *isl_union_flow_free(__isl_take isl_union_flow *flow) in isl_union_flow_free() argument
2110 if (!flow) in isl_union_flow_free()
[all …]
H A Dflow.c24 isl_union_flow *flow; in main() local
32 flow = isl_union_access_info_compute_flow(access); in main()
36 p = isl_printer_print_union_flow(p, flow); in main()
39 isl_union_flow_free(flow); in main()
H A Dflow_test.sh.in8 for i in $srcdir/test_inputs/flow/*.ai; do
11 test=test-$base.flow
13 ref=$dir/$base.flow
/llvm-project/polly/lib/External/isl/include/isl/
H A Dflow.h117 isl_ctx *isl_union_flow_get_ctx(__isl_keep isl_union_flow *flow);
119 __isl_keep isl_union_flow *flow);
122 __isl_keep isl_union_flow *flow);
125 __isl_keep isl_union_flow *flow);
128 __isl_keep isl_union_flow *flow);
131 __isl_keep isl_union_flow *flow);
134 __isl_keep isl_union_flow *flow);
137 __isl_keep isl_union_flow *flow);
138 __isl_null isl_union_flow *isl_union_flow_free(__isl_take isl_union_flow *flow);
141 __isl_take isl_printer *p, __isl_keep isl_union_flow *flow);
[all …]
/llvm-project/mlir/test/Dialect/Bufferization/Transforms/OwnershipBasedBufferDeallocation/
H A Dinvalid-buffer-deallocation.mlir4 // Test Case: explicit control-flow loop with a dynamically allocated buffer.
6 // control-flow loop since they are not supported.
8 // expected-error@+1 {{Only structured control-flow loops are supported}}
37 // Test Case: explicit control-flow loop with a dynamically allocated buffer.
39 // control-flow loop since they are not supported.
41 // expected-error@+1 {{Only structured control-flow loops are supported}}
/llvm-project/llvm/docs/
H A DCFIVerify.rst14 indirect control flow operations are protected by CFI, and should output these
33 indirect control flow instructions are identified.
44 Unprotected indirect control flow instructions will be flagged for manual
64 The tool would operate by searching for indirect control flow instructions in
65 the disassembly. A control flow graph would be generated from a small buffer of
66 the instructions surrounding the 'target' control flow instruction. If the
70 conditional jump target should be the CFI trap. If an indirect control flow
87 present in these sections has already violated the control flow integrity.
90 control flow operations across DSO boundaries. Currently, these CFI features are
/llvm-project/clang/docs/
H A DDataFlowAnalysisIntro.md1 # Data flow analysis: an informal introduction
5 This document introduces data flow analysis in an informal way. The goal is to
9 Data flow analysis is a well-established technique; it is described in many
31 ## Data flow analysis
33 ### The purpose of data flow analysis
35 Data flow analysis is a static analysis technique that proves facts about a
37 program, while taking control flow into account and scaling to large programs.
39 control flow graph (CFG) until a fixpoint is reached.
43 We would like to explain data flow analysis while discussing an example. Let's
68 us to make a conclusion that `x` can only have one value. When control flow from
[all …]
H A DDataFlowSanitizer.rst16 DataFlowSanitizer is a generalised dynamic data flow analysis.
20 dynamic data flow analysis framework to be used by clients to help
31 libc++ and the libc++ ABI with data flow sanitizer instrumentation.
56 the propagation of tags through the program according to its data flow.
193 * ``-dfsan-track-select-control-flow`` -- Controls whether to track the control
194 flow of select instructions. Its default value is true. For example:
218 callbacks for control flow conditional expressions.
229 expression for control flow (such as an if's condition).
358 dfsan_print_origin_trace(&j, "A flow from i to j");
364 Taint value 0x1 (at 0x7ffd42bf415c) origin tracking (A flow from i to j)
/llvm-project/mlir/include/mlir/Interfaces/
H A DControlFlowInterfaces.td10 // about control flow operations, e.g. branches.
28 This interface is meant to model well-defined cases of control-flow of
29 value propagation, where what occurs along control-flow edges is assumed to
32 `areTypesCompatible` can be implemented to compare types along control-flow
94 This method is called to compare types along control-flow edges. By
122 expressing control flow information for region holding operations.
124 This interface is meant to model well-defined cases of control-flow and
125 value propagation, where what occurs along control-flow edges is assumed to
136 "successor operands" are forwarded to. In the latter case, the control flow
190 Note: The control flow doe
[all...]
/llvm-project/llvm/test/Analysis/DependenceAnalysis/
H A DBanerjee.ll23 ; CHECK-NEXT: da analyze - flow [<= <>]!
37 ; NORMALIZE-NEXT: da analyze - flow [<= <>]!
51 ; DELIN-NEXT: da analyze - flow [<= <>]!
108 ; CHECK-NEXT: da analyze - flow [* <>]!
122 ; NORMALIZE-NEXT: da analyze - flow [* <>]!
136 ; DELIN-NEXT: da analyze - flow [* <>]!
295 ; CHECK-NEXT: da analyze - flow [> >]!
323 ; DELIN-NEXT: da analyze - flow [> >]!
465 ; CHECK-NEXT: da analyze - flow [< <]!
479 ; NORMALIZE-NEXT: da analyze - flow [< <]!
[all...]
H A DExactSIV.ll18 ; CHECK-NEXT: da analyze - flow [<=|<]!
150 ; CHECK-NEXT: da analyze - flow [>]!
193 ; CHECK-NEXT: da analyze - flow [>]!
236 ; CHECK-NEXT: da analyze - flow [=>|<]!
279 ; CHECK-NEXT: da analyze - flow [=>|<]!
322 ; CHECK-NEXT: da analyze - flow [*|<]!
408 ; CHECK-NEXT: da analyze - flow [>]!
451 ; CHECK-NEXT: da analyze - flow [>]!
494 ; CHECK-NEXT: da analyze - flow [=>|<]!
537 ; CHECK-NEXT: da analyze - flow [
[all...]
/llvm-project/llvm/test/YAMLParser/
H A Dspec-09-12.test3 # Outside flow collection:
7 # Inside flow collection:
H A Dplain-characters.test4 # Outside flow collection:
10 # Inside flow collection:
/llvm-project/mlir/include/mlir/Transforms/
H A DPasses.td38 "Perform control flow optimizations to the region tree",
41 "Don't run any control-flow simplification."),
43 "Perform simple control-flow simplifications (e.g. dead args elimination)."),
45 "Perform aggressive control-flow simplification (e.g. block merging).")
57 def ControlFlowSink : Pass<"control-flow-sink"> {
60 This pass implements control-flow sink on operations that implement
68 control-flow sink uses a simple and conversative cost model: operations are
377 This pass only supports unstructured control-flow. Promotion of operations
384 "Perform control flow optimizations to the region tree">,
531 - Uses (data flow) a
[all...]
/llvm-project/mlir/include/mlir/IR/
H A DRegionKindInterface.td25 control flow semantics. RegionKind::SSACFG represents an
26 [SSA-style control flow](../LangRef.md/#modeling-control-flow) region
/llvm-project/llvm/test/CodeGen/AMDGPU/
H A Dtransform-block-with-return-to-epilog.ll127 ; GCN-NEXT: bb.3.flow.preheader:
134 ; GCN-NEXT: bb.4.flow:
174 br i1 %cmp0, label %kill0, label %flow
180 flow: ; preds = %entry
182 br i1 %cmp1, label %flow, label %end
184 kill1: ; preds = %flow
188 end: ; preds = %kill0, %kill1, %flow
/llvm-project/mlir/include/mlir/Dialect/Transform/Transforms/
H A DPasses.td23 The pass is capable of handling branching control flow and reports all
25 reported if at least one of the control flow paths between the definition of
28 flow analysis to prove that some branches are not taken, however, SCCP and
29 other control flow simplifications can be performed on the transform IR
31 control flow interfaces.
/llvm-project/llvm/test/Transforms/SampleProfile/
H A Dcsspgo-import-list.ll2 …mple-profile-file=%S/Inputs/csspgo-import-list.prof --sample-profile-even-flow-distribution=0 -S |…
4 …go-sample-use-pipeline -sample-profile-file=%t.prof --sample-profile-even-flow-distribution=0 -S |…
7 …pgo-sample-use-pipeline -sample-profile-file=%t.md5 --sample-profile-even-flow-distribution=0 -S |…
12 …o-import-list.prof -profile-summary-hot-count=10000 --sample-profile-even-flow-distribution=0 -S |…
14 …eplay-scope=Module -profile-summary-hot-count=10000 --sample-profile-even-flow-distribution=0 -S |…
16 …eplay-scope=Module -profile-summary-hot-count=10000 --sample-profile-even-flow-distribution=0 -S |…
/llvm-project/mlir/docs/
H A DLangRef.md234 [SSA control flow semantics](#control-flow-and-ssacfg-regions) is constrained
372 [SSACFG regions](#control-flow-and-ssacfg-regions), each block represents a
375 implement control flow branches between basic blocks.
378 [terminator operation](#control-flow-and-ssacfg-regions). A region with a single
390 [control flow](#control-flow-and-ssacfg-regions), MLIR leverages this structure
391 to implicitly represent the passage of control-flow dependent values without the
393 values which are not control-flow dependent can be referenced directly and do
441 regions: [SSACFG regions](#control-flow-and-ssacfg-regions), which describe
442 control flow between blocks, and [Graph regions](#graph-regions), which do not
443 require control flow between block. The kinds of regions within an operation are
[all …]
/llvm-project/llvm/tools/llvm-exegesis/lib/
H A DBenchmarkResult.cpp168 static const bool flow = false;
187 static const bool flow = true; in mustQuote()
192 static const bool flow = false;
216 // exegesis::Measure is rendererd as a flow instead of a list.
229 static const bool flow = true; in mapping()
244 static const bool flow = false;
278 static const bool flow = true; in input()
170 static const bool flow = false; global() member
189 static const bool flow = true; global() member
194 static const bool flow = false; global() member
231 static const bool flow = true; global() member
248 static const bool flow = false; global() member
282 static const bool flow = true; global() member
/llvm-project/clang-tools-extra/docs/clang-tidy/checks/readability/
H A Dredundant-control-flow.rst1 .. title:: clang-tidy - readability-redundant-control-flow
3 readability-redundant-control-flow
/llvm-project/llvm/test/Instrumentation/SanitizerCoverage/
H A Dcontrol-flow.ll1 ; Test -sanitizer-coverage-control-flow.
2 …dule(sancov-module)' -sanitizer-coverage-level=3 -sanitizer-coverage-control-flow -S | FileCheck %s
/llvm-project/mlir/test/Transforms/
H A Dcontrol-flow-sink-test.mlir1 // Invoke the test control-flow sink pass to test the utilities.
2 // RUN: mlir-opt -test-control-flow-sink %s | FileCheck %s
/llvm-project/llvm/test/Transforms/GVN/PRE/
H A Dlocal-pre.ll32 ; Don't PRE across implicit control flow.
60 ; Don't PRE across implicit control flow.
121 ; It is OK to PRE across implicit control flow if we don't insert new
/llvm-project/llvm/include/llvm/CodeGen/
H A DMIRYamlMapping.h214 static const bool flow = true;
235 static const bool flow = true;
309 static const bool flow = true;
333 static const bool flow = true;
412 static const bool flow = true;
498 static const bool flow = true;
516 static const bool flow = true;
542 static const bool flow = true;

12345678910>>...18