Searched refs:approach (Results 1 – 25 of 262) sorted by relevance
1234567891011
| /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/valgrind/none/tests/ |
| D | resolv.vgtest | 1 # Disabled on Solaris because different approach needs to be taken.
|
| /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/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/skia/dm/ |
| D | DMSrcSink.h | 61 enum Approach { kDirect, kIndirect } approach; member
64 : type(t), approach(a), multisampled(ms) {} in type()
405 flags.approach = SinkFlags::kIndirect; in flags()
|
| D | DMSrcSink.cpp | 103 || flags.approach != SinkFlags::kDirect; in veto()
297 return flags.type != SinkFlags::kRaster || flags.approach != SinkFlags::kDirect; in veto()
796 || flags.approach != SinkFlags::kDirect; in veto()
886 return flags.type != SinkFlags::kGPU || flags.approach != SinkFlags::kDirect || in veto()
890 return flags.type != SinkFlags::kRaster || flags.approach != SinkFlags::kDirect; in veto()
997 return flags.type != SinkFlags::kRaster || flags.approach != SinkFlags::kDirect; in veto()
1190 return !type_ok || flags.approach != SinkFlags::kDirect; in veto()
|
| /external/dagger2/ |
| D | README.md | 9 Dagger 2 is a compile-time evolution approach to dependency injection. Taking the approach
|
| /external/swiftshader/third_party/LLVM/test/Transforms/InstCombine/ |
| D | stack-overalign.ll | 10 ; Abstaining from this transform is not the only way to approach this
|
| /external/valgrind/helgrind/ |
| D | README_YARD.txt | 13 safe write point". As far as I know this is a novel approach. Some
|
| /external/llvm/test/Transforms/InstCombine/ |
| D | stack-overalign.ll | 10 ; Abstaining from this transform is not the only way to approach this
|
| /external/fmtlib/doc/bootstrap/ |
| D | progress-bars.less | 63 // `.progress-bar.active` approach.
|
| /external/zlib/src/contrib/iostream3/ |
| D | README | 16 approach of the standard library's fstream classes. It compiles under gcc versions
|
| /external/valgrind/gdbserver_tests/ |
| D | README_DEVELOPERS | 99 Rational for test approach
102 V: use the 'vg_regtest' approach used by the rest of Valgrind tests
112 template diff approach is quite fragile (e.g. changing the gdb version
|
| /external/bison/m4/ |
| D | configmake.m4 | 21 dnl Copy the approach used in autoconf 2.60.
|
| /external/swiftshader/third_party/LLVM/docs/HistoricalNotes/ |
| D | 2001-06-20-.NET-Differences.txt | 23 compiled by the same compiler, whereas our approach allows us to link and
|
| D | 2001-02-06-TypeNotationDebateResp2.txt | 43 I considered this approach for arrays in general (ie array of int/ array
|
| D | 2001-09-18-OptimizeExceptions.txt | 45 at a time, tree based approach:
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2001-06-20-.NET-Differences.txt | 23 compiled by the same compiler, whereas our approach allows us to link and
|
| D | 2001-02-06-TypeNotationDebateResp2.txt | 43 I considered this approach for arrays in general (ie array of int/ array
|
| D | 2001-09-18-OptimizeExceptions.txt | 45 at a time, tree based approach:
|
| /external/eigen/doc/ |
| D | TutorialReshapeSlicing.dox | 13 … input matrix itself, which is not possible for compile-time sizes, the approach consist in creati…
|
| /external/protobuf/docs/swift/ |
| D | DesignDoc.md | 69 approach. We can unconditionally surround all property names with backticks to
396 Using this approach, proto3 consumers must always have a default case or handle
448 One minor oddity with this approach is that nil will be auto-converted to the
499 the other aliases. One drawback to this approach is that the static aliases
526 This approach fulfills the needs of proto consumers by providing a
634 approach.
670 This approach also has the disadvantage that there is no automatic “short” way
|
| /external/chromium-trace/catapult/telemetry/third_party/mox3/ |
| D | README.rst | 18 approach to running tests is to simply run the command `tox`. This will
|
| /external/llvm/docs/ |
| D | LinkTimeOptimization.rst | 35 The following example illustrates the advantages of LTO's integrated approach
128 link time optimizer significantly, which is not necessary. This approach
131 this approach increases end user's build time due to the duplication of work
|
| /external/libnetfilter_conntrack/ |
| D | README | 15 traditional static filtering approach. The connection tracking system defines
|
1234567891011