Searched refs:approach (Results 1 – 25 of 1041) sorted by relevance
12345678910>>...42
| /external/arm-trusted-firmware/docs/security_advisories/ |
| D | security-advisory-tfv-7.rst | 39 approach by mitigating Variant 4 in hardware wherever possible during secure
54 For affected CPUs, this approach enables the mitigation during EL3
58 This approach permanently mitigates the entire software stack and no additional
61 TF-A implements this approach for the following affected CPUs:
75 For affected CPUs, this approach also enables the mitigation during EL3
76 initialization, following every PE reset. In addition, this approach implements
79 context, where the risk is deemed low enough. This approach enables mitigation
81 on exit from EL3. For more information on this approach, see `Firmware
84 This approach may be complemented by additional mitigation code in other
87 approach will effectively permanently mitigate the entire software stack, since
[all …]
|
| /external/zstd/contrib/match_finders/ |
| D | README.md | 7 * The original motivation for studying this approach was to try and optimize
29 * Note: after some experimentation, this approach proved to not provide enough
31 * where this approach consistenly outperforms Zstandard even on level 19 is
34 * (large similar files) this approach by itself took 5-10X longer than zstd-19 and
36 * over this appraoch for match finding is the overlapping matches. This approach
|
| /external/flatbuffers/docs/source/ |
| D | CUsage.md | 78 the top-down approach.
83 The tutorial uses a bottom up approach. In C it is also possible to use
84 a top-down approach by starting and ending objects nested within each
171 The `FLATBUFFERS_WRAP_NAMESPACE` approach used in the tutorial is convenient
173 the best approach. If the namespace is absent, or simple and
176 mentioned above uses this approach.
|
| /external/linux-kselftest/tools/testing/selftests/net/forwarding/ |
| D | README | 29 This approach for testing switch ASICs has several advantages over the
38 not always available. With the VRF-based approach one merely needs to
|
| /external/tensorflow/tensorflow/lite/delegates/utils/dummy_delegate/ |
| D | README.md | 32 The former approach requires few changes as detailed below. The latter one
36 delegate-registrar approach is slightly preferred here.
41 In this approach, create a delegate provider like the
125 In this **alternative approach to reuse existing Tensorflow Lite kernel testing
138 via this external-delegate approach. We could use similar commands for testing
|
| /external/rust/cxx/tests/ui/ |
| D | async_fn.stderr | 1 …nc function is not directly supported yet, but see https://cxx.rs/async.html for a working approach
|
| /external/ply/ply/ |
| D | TODO | 14 than the reflection approach used by PLY.
|
| /external/perfetto/docs/design-docs/ |
| D | heapprofd-sampling.md | 10 approach that handles a statistically meaningful subset of allocations. This
16 Bernoulli trial. The reason we use a random sampling approach, as opposed to
53 exponential draw approach, as for a non-sample, we only need to decrement a
121 Benchmarking of the STL distributions on a Pixel 4 reinforces our approach of
148 The most obvious impact is that with the old approach we would expect to sample
|
| /external/googletest/googletest/ |
| D | README.md | 66 And a more robust and flexible approach is to build GoogleTest as part of that
76 location. This is the least flexible approach and can make it more difficult
79 source tree. This is often the simplest approach, but is also the hardest to
85 approach doesn't have the limitations of the other methods.
109 Note that this approach requires CMake 3.14 or later due to its use of the
|
| /external/curl/docs/cmdline-opts/ |
| D | proxytunnel.d | 8 the proxy. The tunnel approach is made with the HTTP proxy CONNECT request and
|
| /external/libcap/doc/ |
| D | capability.notes | 11 this fine grained approach to constraining the danger to your system
17 Adopting a role approach to system security:
|
| /external/angle/src/libANGLE/renderer/metal/doc/ |
| D | TransformFeedback.md | 52 - Instead of executing the same Vertex Shader's logic twice, one alternative approach is writing the
60 - However, this approach might even be slower than executing the Vertex Shader twice. Because a
65 enabled, the original approach will just simply executes the Vertex Shader once and use a cheap
|
| /external/llvm-project/mlir/include/mlir/Dialect/Tosa/Transforms/ |
| D | Passes.td | 21 approach similar to step 1 of Numpy 4-step broadcasting:
|
| /external/python/pybind11/docs/advanced/ |
| D | misc.rst | 206 This approach has the potential downside that instances of classes exposed
221 call from Python might lead to undefined behavior). Yet another approach that
241 approach (which also works on CPython) is to use the :py:mod:`atexit` module [#f7]_,
260 simple example repository which uses this approach.
262 There are two potential gotchas when using this approach: first, make sure that
|
| /external/openscreen/cast/cast_core/api/metrics/ |
| D | metrics_recorder.proto | 23 // This repliciates the Fuchsia approach to Cast metrics; for documentation on
|
| /external/icu/tools/srcgen/javadoc_patches/patches/src/main/java/android/icu/util/ |
| D | IslamicCalendar.java.patch | 8 - * which approach is used to determine the start of a month. By default, the
|
| /external/ruy/ruy/profiler/ |
| D | README.md | 18 A discussion of pros/cons of this approach is appended below.
143 Another key aspect determining what profiling approach is suitable for a given
146 instrument the known possibly-critical code as per the present approach. On the
|
| /external/sqlite/ |
| D | Android.bp | 5 // Added automatically by a large-scale-change that took the approach of
|
| /external/ksoap2/ |
| D | Android.bp | 5 // Added automatically by a large-scale-change that took the approach of
|
| /external/gemmlowp/meta/ |
| D | README | 34 The basic kernel used in this approach is of shape 3x3x8. Obviously this
56 This approach allowed moving all unnecessary branching and conditional execution
|
| /external/grpc-grpc/examples/cpp/helloworld/ |
| D | CMakeLists.txt | 33 # This approach is very simple to use, but the are some potential
43 # A more robust approach to add dependency on gRPC is using
|
| /external/python/pyopenssl/doc/ |
| D | internals.rst | 43 methods are declared static. One approach would be to have :py:mod:`.OpenSSL` as
47 importing the :py:mod:`socket` module. The other approach is to somehow get a
|
| /external/shaderc/spirv-headers/ |
| D | Android.bp | 5 // Added automatically by a large-scale-change that took the approach of
|
| /external/scapy/ |
| D | Android.bp | 5 // Added automatically by a large-scale-change that took the approach of
|
| /external/selinux/ |
| D | Android.bp | 5 // Added automatically by a large-scale-change that took the approach of
|
12345678910>>...42