| /external/mesa3d/src/compiler/nir/ |
| D | nir_propagate_invariant.c | 27 add_src(nir_src *src, struct set *invariants) in add_src() argument
30 _mesa_set_add(invariants, src->ssa); in add_src()
32 _mesa_set_add(invariants, src->reg.reg); in add_src()
44 dest_is_invariant(nir_dest *dest, struct set *invariants) in dest_is_invariant() argument
47 return _mesa_set_search(invariants, &dest->ssa); in dest_is_invariant()
49 return _mesa_set_search(invariants, dest->reg.reg); in dest_is_invariant()
54 add_cf_node(nir_cf_node *cf, struct set *invariants) in add_cf_node() argument
58 add_src(&if_stmt->condition, invariants); in add_cf_node()
62 add_cf_node(cf->parent, invariants); in add_cf_node()
66 add_var(nir_variable *var, struct set *invariants) in add_var() argument
[all …]
|
| /external/v8/tools/clang/blink_gc_plugin/ |
| D | README.chromium | 1 This clang plugin checks various invariants of the Blink garbage
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/LoopStrengthReduce/ARM/ |
| D | addrec-is-loop-invariant.ll | 5 ; its operands are loop invariants.
|
| /external/nanopb-c/docs/ |
| D | security.rst | 49 The following invariants are maintained during operation, even if the
|
| /external/grpc-grpc/third_party/nanopb/docs/ |
| D | security.rst | 49 The following invariants are maintained during operation, even if the
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/Inline/ |
| D | inline-tail.ll | 201 ; any tail marking, otherwise we break verifier invariants.
|
| /external/python/cpython3/Doc/howto/ |
| D | functional.rst | 112 The technique used to prove programs correct is to write down **invariants**,
114 true. For each line of code, you then show that if invariants X and Y are true
115 **before** the line is executed, the slightly different invariants X' and Y' are
117 the program, at which point the invariants should match the desired conditions
121 difficult to handle with this technique; assignments can break invariants that
122 were true before the assignment without producing any new invariants that can be
|
| /external/python/cpython2/Doc/howto/ |
| D | functional.rst | 111 The technique used to prove programs correct is to write down **invariants**,
113 true. For each line of code, you then show that if invariants X and Y are true
114 **before** the line is executed, the slightly different invariants X' and Y' are
116 the program, at which point the invariants should match the desired conditions
120 difficult to handle with this technique; assignments can break invariants that
121 were true before the assignment without producing any new invariants that can be
|
| /external/python/cpython2/Misc/NEWS.d/ |
| D | 2.6b3.rst | 169 the rules for hash invariants and were already unhashable in 3.0 have now
|
| /external/clang/test/CodeGenObjCXX/ |
| D | arc.mm | 276 // Just make sure that the AST invariants hold properly here,
|
| /external/tensorflow/tensorflow/core/protobuf/tpu/ |
| D | optimization_parameters.proto | 282 // maintain two invariants during model training:
|
| /external/v8/third_party/v8/builtins/ |
| D | array-sort.tq | 703 // The invariants still hold, so:
1563 // until the stack invariants are re-established:
1598 // Regardless of invariants, merge all runs on the stack until only one
|
| /external/python/cpython3/Doc/library/ |
| D | enum.rst | 422 some important invariants of types and instances. On the other hand, it makes
859 the normal :class:`Enum` invariants (such as not being comparable to other
|
| D | heapq.rst | 206 break the heap structure invariants. So, a possible solution is to mark the
|
| /external/tensorflow/tensorflow/compiler/xla/ |
| D | xla.proto | 75 // correctness and the invariants that must be satisfied by "fully optimized"
|
| /external/python/cpython2/Doc/library/ |
| D | heapq.rst | 194 break the heap structure invariants. So, a possible solution is to mark the
|
| D | email.message.rst | 122 responsibility to ensure the payload invariants. Optional *charset* sets
|
| /external/python/cpython2/Objects/ |
| D | listsort.txt | 330 What turned out to be a good compromise maintains two invariants on the
366 both invariants are satisfied. As an extreme case, suppose we didn't do the
|
| /external/python/cpython3/Objects/ |
| D | listsort.txt | 330 What turned out to be a good compromise maintains two invariants on the
366 both invariants are satisfied. As an extreme case, suppose we didn't do the
|
| /external/clang/docs/analyzer/ |
| D | IPA.txt | 101 fairly poor job of modeling certain data structure invariants of container-like
|
| /external/parameter-framework/upstream/doc/requirements/ |
| D | requirements.md | 144 All parameters have a data type. A data type designates parameter invariants.
173 check parameter validity (invariants) nor a pretty display of the values.</why>
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Analysis/ScalarEvolution/ |
| D | different-loops-recs.ll | 70 ; Check that we can evaluate a sum of phis+invariants from two different loops
|
| /external/e2fsprogs/lib/et/ |
| D | com_err.texinfo | 397 failures of internal invariants and consistency checks only, as it
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | GlobalISel.rst | 612 The pass approach lets us use the ``MachineVerifier`` to enforce invariants.
|
| /external/google-benchmark/ |
| D | README.md | 697 iteration, and/or as per-thread averages, and/or iteration invariants;
|