| /external/autotest/client/site_tests/desktopui_SonicExtension/ |
| D | desktopui_SonicExtension.py | 98 information = {}
100 information['machine_name'] = settings['machine_name']
102 information['machine_name'] = socket.gethostname()
103 information['network_profile'] = settings['network_profile']
104 information['chrome_version'] = self._test_utils.get_chrome_version(
106 information['chrome_revision'] = self._test_utils.get_chrome_revision(
108 information['sonic_build'] = self._sonic_build
109 information['video_name'] = settings.get('video_name',
111 information['comments'] = settings['comments']
112 return information
|
| /external/e2fsprogs/tests/f_resize_inode/ |
| D | expect | 19 Writing superblocks and filesystem accounting information: done
25 Pass 5: Checking group summary information
38 Pass 5: Checking group summary information
53 Pass 5: Checking group summary information
66 Pass 5: Checking group summary information
81 Pass 5: Checking group summary information
94 Pass 5: Checking group summary information
109 Pass 5: Checking group summary information
122 Pass 5: Checking group summary information
135 Pass 5: Checking group summary information
[all …]
|
| /external/e2fsprogs/debian/ |
| D | control.in | 101 See RFC 4122 for more information.
117 See RFC 4122 for more information.
135 See RFC 4122 for more information.
147 See RFC 4122 for more information.
263 Description: debugging information for e2fsprogs
264 This package includes the debug information useful for debugging e2fsprogs
266 The debug information is used for execution tracing and core
274 Description: debugging information for uuid-runtime
275 This package includes the debug information useful for debugging the
277 The debugging information is used for execution tracing and core
[all …]
|
| /external/llvm/docs/ |
| D | SourceLevelDebugging.rst | 11 This document is the central repository for all information pertaining to debug
12 information in LLVM. It describes the :ref:`actual format that the LLVM debug
13 information takes <format>`, which is useful for those interested in creating
14 front-ends or dealing directly with the information. Further, this document
15 provides specific examples of what debug information for C/C++ looks like.
17 Philosophy behind LLVM debugging information
20 The idea of the LLVM debugging information is to capture how the important
25 * Debugging information should have very little impact on the rest of the
27 be modified because of debugging information.
30 ways <intro_debugopt>` with the debugging information.
[all …]
|
| D | LinkTimeOptimization.rst | 97 anywhere. This information is used by the LLVM optimizer and it
115 information collected during the linker's normal symbol resolution phase.
120 **Use separate tool to collect symbol information from all object files.**
122 capability to collect information for link time optimization. Not only is
137 The linker collects information about symbol definitions and uses in various
138 link objects which is more accurate than any information collected by other
139 tools during typical build cycles. The linker collects this information by
141 symbol visibility information. The linker also uses user-supplied information,
143 information, data flow information and knows much more about program structure
145 integration between the linker and the optimizer by sharing this information
[all …]
|
| D | AliasAnalysis.rst | 25 analysis information and the implementations providing it, and is designed to
28 information, this class exposes Mod/Ref information from those implementations
32 This document contains information necessary to successfully implement this
46 The ``AliasAnalysis`` interface exposes information about memory, represented in
51 get mod/ref information for arbitrary instructions.
99 ``&C[0]`` element is a two byte access. If size information wasn't available in
145 The ``getModRefInfo`` methods return information about whether the execution of
146 an instruction can read or modify a memory location. Mod/Ref information is
161 Several other tidbits of information are often collected by various alias
169 (functions, constant global variables, and the null pointer). This information
[all …]
|
| /external/autotest/site_utils/rpm_control_system/ |
| D | rpm_config.ini | 16 # General RPM infrastructure information.
26 # Size of the LRU that holds power management unit information related
31 # Access information for Sentry Based Devices.
38 # Access information for Web Powered Devices.
43 # Acess information for POE Switches.
|
| /external/libxml2/doc/ |
| D | docdescr.doc | 6 to save others some time by setting down the basic information about how
8 but will keep this document up-to-date for everyone's information. Note
14 generated using the information present in these core files, plus the
35 using information from libxml2-api.xml and libxml2-refs.xml
60 Instead of using the information from the gtk-doc routines, it actually
61 re-processes all the the library source files, extracting information
62 about the api (exported procedures and symbols, together with information
64 contains all of this information, "libxml2-api.xml".
71 information on the api's in the file "libxml2-api.xml", but that step is
|
| /external/icu/android_icu4j/runner/src/main/java/android/icu/junit/ |
| D | IcuFrameworkTest.java | 105 String information = stringWriter.toString(); in test_for_TestFmwk_Run() local
108 Matcher matcher = EXTRACT_ERROR_INFO.matcher(information); in test_for_TestFmwk_Run()
110 information = matcher.group(1)/*.replace("\n ", "\n")*/; in test_for_TestFmwk_Run()
115 + errorCount + " error(s)\n" + information; in test_for_TestFmwk_Run()
|
| /external/google-breakpad/src/processor/proto/ |
| D | process_state.proto | 81 // information, this will point to the thread that requested the dump.
100 // "Mac OS X", or "Linux". If the information is present in the dump but
102 // the information is not present in the dump, this field will be empty.
107 // "mac", and "linux". Empty if the information is not present in the dump
114 // contain this information, this field will be empty.
118 // If this information is present in the dump but its value is unknown,
119 // this field will contain a numeric value. If the information is not
125 // "GenuineIntel level 6 model 13 stepping 8". If the information is not
126 // present in the dump, or additional identifying information is not
173 // Carries information about code modules that are loaded into a process.
[all …]
|
| /external/llvm/test/CodeGen/X86/ |
| D | stackmap-liveness.ll | 28 ; StackMap 1 (no liveness information available)
39 ; StackMap 1 (patchpoint liveness information enabled)
59 ; StackMap 2 (no liveness information available)
70 ; StackMap 2 (patchpoint liveness information enabled)
103 ; StackMap 3 (no liveness information available)
114 ; StackMap 3 (patchpoint liveness information enabled)
140 ; StackMap 4 (patchpoint liveness information enabled)
151 ; StackMap 5 (patchpoint liveness information enabled)
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2000-12-06-MeetingSummary.txt | 15 analysis because the extra information can help limit the scope of
19 * Including this information would require that all users of the LLVM
28 information for one optimization. Alias analysis itself is typically
38 1. Including dominator information in the LLVM bytecode
45 2. Including loop header and body information. This would facilitate
65 packet type and length field before analysis information, to allow a
66 runtime to skip information that it didn't understand in a bytecode
|
| /external/curl/ |
| D | curl-config.in | 44 --libs library linking information
47 --static-libs static libcurl library linking information
48 --version output version information
49 --vernum output the version information as a number (hexadecimal)
|
| /external/e2fsprogs/debugfs/ |
| D | ro_debug_cmds.ct | 39 request do_stat, "Show inode information ",
42 request do_dump_extents, "Dump extents information ",
48 request do_filefrag, "Report fragmentation information for an inode",
87 request do_dump_mmp, "Dump MMP information",
|
| /external/v8/tools/ |
| D | v8-rolls.sh | 43 Run in chromium/src to get information about V8 rolls.
47 -n Number of rolls to print information about.
48 -s Chromium git hash to start printing V8 information about.
|
| /external/iproute2/doc/ |
| D | nstat.sgml | 49 <item><tt/-e/ - display extended information about errors (<tt/ifstat/ only).
63 or source of information switched between different instances
79 of source of information, it may be word <tt/kernel/, when <tt/Xstat/
80 gets information from kernel or some dotted decimal number followed
81 by parameters, when it obtains information from running <tt/Xstat/ daemon.
100 Client <tt/Xstat/, before trying to get information from the kernel,
103 none of them replied it gets information from kernel.
|
| /external/e2fsprogs/tests/f_special_ea/ |
| D | expect.1 | 1 Backing up journal inode block information.
7 Pass 5: Checking group summary information
|
| /external/e2fsprogs/tests/f_bad_local_jnl/ |
| D | expect.1 | 4 Backing up journal inode block information.
10 Pass 5: Checking group summary information
|
| /external/google-breakpad/src/testing/scripts/generator/ |
| D | README | 3 For more information about cppclean, see the README.cppclean file or
31 classes, the template information is lost. You will need to add the template
32 information manually.
|
| /external/harfbuzz_ng/ |
| D | README | 7 For bug reports, mailing list, and other information please visit:
11 For license information, see the file COPYING.
|
| D | README.md | 7 For bug reports, mailing list, and other information please visit:
11 For license information, see the file COPYING.
|
| /external/llvm/docs/TableGen/ |
| D | index.rst | 20 domain-specific information. Because there may be a large number of these
24 it easier to structure domain specific information.
82 that extracts the information specific to what you need and formats it in the
150 encoding, etc. The contents and semantics of the information in the record are
153 As you can see, a lot of information is needed for every instruction supported
156 TableGen, all of the information was derived from the following definition:
172 they prefer to use when describing their information.
196 record; it is this that holds the domain specific information for the
259 information on the usage of the language, and the
270 of running ``llvm-tblgen`` is to print the information in a textual format, but
[all …]
|
| /external/zlib/src/win32/ |
| D | README-WIN32.txt | 33 example.pdb Symbolic information for debugging example.exe
36 example_d.pdb Symbolic information for debugging example_d.exe
39 minigzip.pdb Symbolic information for debugging minigzip.exe
42 minigzip_d.pdb Symbolic information for debugging minigzip_d.exe
102 the file ChangeLog history information documenting your changes. Please read
103 the FAQ for more information on the distribution of modified source versions.
|
| /external/chromium-trace/catapult/third_party/webapp2/docs/tutorials/gettingstarted/ |
| D | handlingforms.rst | 6 process information submitted by the user with a web form. The ``webapp2``
64 for more information.
72 …when attempted. For more information, see `The Python Runtime Environment <http://code.google.com/…
77 Now that we can collect information from the user, we need a place to put it
|
| /external/jacoco/jacoco-maven-plugin.test/it/it-report-without-debug/ |
| D | verify.bsh | 16 if ( buildLog.indexOf( "with debug information" ) < 0 ) {
17 throw new RuntimeException( "No warning about debug information" );
|