Searched full:difficult (Results 1 – 25 of 1784) sorted by relevance
12345678910>>...72
| /external/tensorflow/tensorflow/lite/tools/evaluation/stages/utils/ |
| D | image_metrics.h | 66 bool difficult = false;
74 : difficult(d), imgid(id), score(s), box(b) {} in Detection()
76 : difficult(d), imgid(id), score(s), box(b), ignore(i) {} in Detection()
112 // 'difficult' is a special bit specific to Pascal VOC dataset and tasks using
113 // the data. If 'difficult' is true, by convention, the box is often ignored
114 // during the AP calculation. I.e., if a predicted box matches a 'difficult'
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2001-02-06-TypeNotationDebateResp1.txt | 13 and him that the C declarator syntax is difficult and confusing.
32 particular problem is inherently difficult. Your syntax for the above
43 make function pointers easier but makes arrays much more difficult seems
54 and Windows are two classic examples of bad technology that are difficult to
|
| D | 2001-02-06-TypeNotationDebateResp4.txt | 25 > particular problem is inherently difficult. Your syntax for the above
64 > make function pointers easier but makes arrays much more difficult seems
69 above does not make arrays any more difficult to use, and makes the
80 > and Windows are two classic examples of bad technology that are difficult to
|
| /external/clang/www/ |
| D | comparison.html | 23 difficult to fix for architectural or political reasons.</p>
73 it extremely difficult to use as an API and integrate into other tools.
77 makes it difficult to decouple the front-end from the rest of the
79 <li>Various GCC design decisions make it very difficult to reuse: its build
80 system is difficult to modify, you can't link multiple targets into one
147 very difficult to use part of Elsa without the whole front-end. For
152 difficult to accurately map from a source location in the AST back to
186 extremely difficult to use it for source analysis tools.</li>
|
| /external/cronet/stable/third_party/protobuf/java/core/src/main/java/com/google/protobuf/ |
| D | ByteOutput.java | 65 * programming error and will lead to data corruption which will be difficult to debug.
80 * programming error and will lead to data corruption which will be difficult to debug.
95 * programming error and will lead to data corruption which will be difficult to debug.
109 * programming error and will lead to data corruption which will be difficult to debug.
|
| /external/protobuf/java/core/src/main/java/com/google/protobuf/ |
| D | ByteOutput.java | 65 * programming error and will lead to data corruption which will be difficult to debug.
80 * programming error and will lead to data corruption which will be difficult to debug.
95 * programming error and will lead to data corruption which will be difficult to debug.
109 * programming error and will lead to data corruption which will be difficult to debug.
|
| /external/cronet/tot/third_party/protobuf/java/core/src/main/java/com/google/protobuf/ |
| D | ByteOutput.java | 65 * programming error and will lead to data corruption which will be difficult to debug.
80 * programming error and will lead to data corruption which will be difficult to debug.
95 * programming error and will lead to data corruption which will be difficult to debug.
109 * programming error and will lead to data corruption which will be difficult to debug.
|
| /external/AFLplusplus/instrumentation/ |
| D | README.lto.md | 163 ## Solving difficult targets
165 Some targets are difficult because the configure script does unusual stuff that
213 Building jsc is difficult as the build script has bugs.
293 `./configure`, see `Solving difficult targets` above.
308 difficult with a program that has so many paths and therefore so many
|
| /external/cronet/tot/third_party/ced/src/util/ |
| D | port.h | 31 // to get the INTn_C and UINTn_C macros for integer constants. It's difficult
32 // to guarantee any specific ordering of header includes, so it's difficult to
|
| /external/cronet/stable/third_party/ced/src/util/ |
| D | port.h | 31 // to get the INTn_C and UINTn_C macros for integer constants. It's difficult
32 // to guarantee any specific ordering of header includes, so it's difficult to
|
| /external/perfmark/doc/ |
| D | fix-stop-task.md | 123 the skew problems are still present. Trying to solve this is difficult without
142 ## Agent Byte Code is more difficult
146 when instrumenting classes. However, it's difficult to rewrite this byte code
|
| /external/dtc/ |
| D | README.license | 41 other environments with unusual technical constraints. It's difficult
43 libfdt into such environments and so difficult to suitably word a
|
| /external/sdv/vsomeip/third_party/boost/config/doc/ |
| D | rationale.qbk | 19 difficult to maintain and more difficult to use safely. You can find a
|
| /external/rust/android-crates-io/crates/mockall/ |
| D | README.md | 15 inject edge and error cases that would be difficult or impossible to create
18 Statically typed languages are inherently more difficult to
|
| /external/cldr/docs/site/index/cldr-spec/ |
| D | definitions.md | 9 … on a computer, smartphone, or similar devices. Reliable information is difficult to obtain; the i…
11 …gularity would be measured as "7\-day actives". Reliable information is difficult to obtain; the i…
|
| /external/sdv/vsomeip/third_party/boost/phoenix/doc/ |
| D | maintenance.qbk | 92 One type of bug which has been very difficult to understand has been that some test cases failed wh…
110 * The most difficult problems to diagnose have been some which occur when the compilation uses opti…
114 * This has made the identification of the cause of the problems more difficult.
|
| /external/ltp/doc/developers/ |
| D | build_system.rst | 12 The problem with the old Makefile system is that it was very difficult to
14 and including new targets was more difficult than it should have been
120 This makes cross-compilation and determinism difficult, if not impossible.
|
| /external/pigweed/pw_channel/ |
| D | design.rst | 44 In practice, this is very difficult to work with:
57 The result is inefficient code that is difficult to write correctly.
128 difficult or impossible to reused application code between e.g. a UART-based
|
| /external/zstd/tests/fuzz/ |
| D | decompress_cross_format.c | 74 // NOTE: this is nice-to-have, please disable this check if it is difficult to satisfy. in LLVMFuzzerTestOneInput()
107 // NOTE: this is nice-to-have, please disable this check if it is difficult to satisfy. in LLVMFuzzerTestOneInput()
|
| /external/pigweed/docs/blog/ |
| D | 06-better-cpp-toolchains.rst | 55 Why is it this difficult?
62 difficult to understand how all the moving pieces of toolchains interact. For
65 surprisingly difficult because of the sheer amount of Bazel implementation
87 * The declared toolchain configuration was quite rigid, so it was difficult to
|
| /external/rust/android-crates-io/crates/crossbeam-channel/src/ |
| D | counter.rs | 53 // counter. It's very difficult to recover sensibly from such degenerate scenarios so we in acquire()
108 // counter. It's very difficult to recover sensibly from such degenerate scenarios so we in acquire()
|
| /external/zxing/core/src/test/resources/blackbox/pdf417-2/ |
| D | 16.txt | 1 A larger PDF 417 barcode with a greater amount of text. This is a more difficult test for mobile de…
|
| D | 17.txt | 1 A larger PDF 417 barcode with a greater amount of text. This is a more difficult test for mobile de…
|
| D | 21.txt | 1 A larger PDF 417 barcode with a greater amount of text. This is a more difficult test for mobile de…
|
| D | 23.txt | 1 A larger PDF 417 barcode with a greater amount of text. This is a more difficult test for mobile de…
|
12345678910>>...72