/llvm-project/mlir/docs/Tools/ |
H A D | mlir-reduce.md | 25 to the tree traversal strategy. The different strategies may lead to different 27 `-reduction-tree='traversal-mode=0'` to select the mode for example. 49 mlir-reduce $INPUT -reduction-tree='traversal-mode=0 test=$TEST_SCRIPT' 122 * `-reduction-tree` now only supports `Single-Path` traversal mode, extends it 123 with different traversal strategies may reduce the input better.
|
/llvm-project/mlir/lib/Analysis/ |
H A D | TopologicalSortUtils.cpp | 161 llvm::ReversePostOrderTraversal<Block *> traversal(&b); in getBlocksSortedByDominance() local 162 blocks.insert(traversal.begin(), traversal.end()); in getBlocksSortedByDominance()
|
/llvm-project/mlir/include/mlir/Reducer/ |
H A D | Passes.td | 33 Option<"traversalModeId", "traversal-mode", "unsigned", 35 "The graph traversal mode, the default is single-path mode">,
|
/llvm-project/llvm/test/Transforms/StructurizeCFG/workarounds/ |
H A D | needs-unified-loop-exits.ll | 4 ; The structurizer uses an RPO traversal over a region, along with a 15 ; any confusion in the hacked RPO traversal. 19 ; the incorrect traversal, B1 dominates all the blocks in the 96 ; traversal, H2 dominates H3 in the structurized program, and the
|
/llvm-project/mlir/test/mlir-reduce/ |
H A D | simple-test.mlir | 2 // RUN: mlir-reduce %s -reduction-tree='traversal-mode=0 test=%S/test.sh'
|
H A D | crashop-reduction.mlir | 2 // RUN: mlir-reduce %s -reduction-tree='traversal-mode=0 test=%S/failure-test.sh' | FileCheck %s
|
H A D | multiple-function.mlir | 2 // RUN: mlir-reduce %s -reduction-tree='traversal-mode=0 test=%S/failure-test.sh' | FileCheck %s
|
/llvm-project/clang/test/Analysis/ |
H A D | retain-release-cache-out.m | 4 // checkers, testing that the traversal order in the CFG does not affect the
|
/llvm-project/llvm/test/Transforms/StructurizeCFG/ |
H A D | post-order-traversal-bug.ll | 3 ; The structurize cfg pass used to do a post-order traversal to generate a list 6 ; The fix for this was to do a reverse post-order traversal which is what the
|
H A D | interleaved-loop-order.ll | 5 ; for which there is an interleaved post-order traversal. 155 ; interleaved post-order traversal.
|
/llvm-project/compiler-rt/lib/xray/ |
H A D | xray_profiling_flags.inc | 21 "Maximum size of the traversal stack allocator.")
|
/llvm-project/llvm/test/Other/ |
H A D | cgscc-disconnected-invalidation.ll | 2 ; graph mid-traversal and then invalidate it function correctly.
|
/llvm-project/llvm/test/Bitcode/ |
H A D | mdnodes-distinct-nodes-break-cycles.ll | 7 ; entry point is !2, a naive post-order traversal would give !3, !1, !2; but
|
H A D | metadata-function-blocks.ll | 19 ; Each node gets a new number. Bottom-up traversal of nodes.
|
/llvm-project/llvm/test/CodeGen/ARM/ |
H A D | 2011-04-27-IfCvtBug.ll | 6 ; traversal of all BBs work just fine.
|
/llvm-project/clang/docs/ |
H A D | LibClang.rst | 62 The elements of an AST can be recursively visited with pre-order traversal with ``clang_visitChildr… 89 #. ``CXChildVisit_Break``: Terminates the cursor traversal 91 #. ``CXChildVisit_Continue``: Continues the cursor traversal with the next sibling of the cursor ju…
|
H A D | IntroductionToTheClangAST.rst | 86 It allows traversal of the whole translation unit starting from
|
H A D | RAVFrontendAction.rst | 82 // Return false to stop the traversal of the AST.
|
/llvm-project/mlir/docs/Tutorials/ |
H A D | UnderstandingTheIRStructure.md | 13 and so will our traversal: 27 wraps a list of `Operation`s. Our traversal will follow this structure with 203 `AllocOp` nested inside the function and interrupt the traversal if one of them
|
/llvm-project/llvm/test/Transforms/LoopPredication/ |
H A D | unswitch-exit-loop.ll | 21 ;; synthetic corner case that demonstrates the need for more careful traversal
|
/llvm-project/clang/test/Modules/ |
H A D | crash-vfs-path-traversal.m | 4 // FIXME: Canonicalizing paths to remove relative traversal components
|
/llvm-project/mlir/docs/ |
H A D | PatternRewriter.md | 330 The driver performs a post-order traversal. Note that it walks regions of the 371 * Top-down traversal: Traverse the container op/region top down and in 373 * Bottom-up traversal: This is the default setting. It builds the initial 374 worklist with a postorder traversal and then reverses the worklist. This may
|
/llvm-project/mlir/include/mlir/Dialect/Linalg/IR/ |
H A D | LinalgInterfaces.td | 733 (i.e. the data traversal order) is not a simple permutation of the loop 734 traversal order. It is then possible to define ops with skewed data 735 traversal order for which we can still easily compute hyperrectangular
|
/llvm-project/clang/docs/analyzer/developer-docs/ |
H A D | DebugChecks.rst | 47 path traversal. This is indented to show the call stack, but does NOT do any 52 during a path traversal ("IfStmt", "WhileStmt", etc). Currently used to check
|
/llvm-project/llvm/test/CodeGen/AMDGPU/ |
H A D | si-lower-i1-copies-order-of-phi-incomings.mir | 7 # traversal. Because of that, incomings in phis created by SDAG are sorted,
|