| /external/llvm-project/openmp/cmake/DetectTestCompiler/ |
| D | CMakeLists.txt | 8 set(information "${CMAKE_${lang}_COMPILER}") variable
9 set(information "${information}\\;${CMAKE_${lang}_COMPILER_ID}") variable
10 set(information "${information}\\;${CMAKE_${lang}_COMPILER_VERSION}") variable
11 set(information "${information}\\;${${lang}_FLAGS}") variable
12 set(information "${information}\\;${${lang}_HAS_TSAN_FLAG}") variable
13 file(WRITE ${CMAKE_CURRENT_BINARY_DIR}/${lang}CompilerInformation.txt ${information})
|
| /external/llvm-project/llvm/docs/PDB/ |
| D | ModiStream.rst | 14 information about a single module (object file, import library, etc that
15 contributes to the binary this PDB contains debug information about. There
18 for a single module contains line information for the compiland, as well as
19 all CodeView information for the symbols defined in the compiland. Finally,
45 meaning that this module has C13 line information (as opposed to C11 line
46 information). A corollary of this is that we expect to only ever see
54 - **C11LineInfo** - A block containing CodeView line information in C11
58 information is not present. As mentioned previously, the format of
62 - **C13LineInfo** - A block containing CodeView line information in C13
66 information is not present.
[all …]
|
| /external/e2fsprogs/tests/f_resize_inode/ |
| D | expect | 8 Writing superblocks and filesystem accounting information: done
14 Pass 5: Checking group summary information
27 Pass 5: Checking group summary information
42 Pass 5: Checking group summary information
55 Pass 5: Checking group summary information
70 Pass 5: Checking group summary information
83 Pass 5: Checking group summary information
98 Pass 5: Checking group summary information
111 Pass 5: Checking group summary information
124 Pass 5: Checking group summary information
[all …]
|
| /external/cldr/tools/java/org/unicode/cldr/util/data/ |
| D | PathDescription.txt | 9 …pe="([^"]*)"]/exemplarCity ; ROOT timezone ; The name of {0}. For more information, see http://cld…
11 …e; The name of the language with Unicode language code = {0}. For more information, see http://cld…
12 …f the script (writing system) with Unicode script code = {0}. For more information, see http://cld…
13 …name of the country or region with Unicode region code = {0}. For more information, see http://cld…
14 … the country subdivision with Unicode subdivision code = {0}. For more information, see http://cld…
15 …The symbol for the currency with the ISO currency code = {0}. For more information, see http://cld…
16 …y, this does not need to be changed from the inherited value. For more information, see http://cld…
17 …lly occurs shortly after a new currency symbol is introduced. For more information, see http://cld…
18 …y; The name of the currency with the ISO currency code = {0}. For more information, see http://cld…
24 …([^"]*)"] ; The name of “{1} collation” (sorting order). For more information, please see htt…
[all …]
|
| /external/e2fsprogs/tests/t_dangerous/ |
| D | expect | 10 Writing superblocks and filesystem accounting information: done
29 Writing superblocks and filesystem accounting information: done
35 Pass 5: Checking group summary information
52 Pass 5: Checking group summary information
69 Pass 5: Checking group summary information
80 Backing up journal inode block information.
95 Pass 5: Checking group summary information
108 Writing superblocks and filesystem accounting information: done
114 Pass 5: Checking group summary information
|
| /external/e2fsprogs/tests/t_iexpand_mcsum/ |
| D | expect | 10 Writing superblocks and filesystem accounting information: done
16 Pass 5: Checking group summary information
27 Backing up journal inode block information.
34 Pass 5: Checking group summary information
54 Pass 5: Checking group summary information
|
| /external/autotest/site_utils/rpm_control_system/ |
| D | rpm_config.ini | 16 # General RPM infrastructure information.
24 # Size of the LRU that holds power management unit information related
29 # Access information for Sentry Based Devices.
36 # Access information for Web Powered Devices.
41 # Acess information for POE Switches.
|
| /external/llvm-project/llvm/docs/CommandGuide/ |
| D | llvm-size.rst | 1 llvm-size - print size information
14 :program:`llvm-size` is a tool that prints size information for binary files.
17 The tool prints size information for each ``input`` specified. If no input is
18 specified, the program prints size information for ``a.out``. If "``-``" is
20 input stream. If an input is an archive, size information will be displayed for
32 Architecture(s) from Mach-O universal binaries to display information for.
50 Display verbose address and offset information for segments and sections in
77 Sysv output displays size and address information for most sections, with each
105 format. When producing ``darwin`` format, the tool displays information about
142 Display size information in the specified radix. Permitted values are ``8``,
|
| D | dsymutil.rst | 14 :program:`dsymutil` links the DWARF debug information found in the object files
15 for an executable *executable* by using debug symbols information contained in
16 its symbol table. By default, the linked debug information is placed in a
28 Link DWARF debug information only for specified CPU architecture types.
38 debug information) in YAML format and exit. Not DWARF link will take place.
98 information.
144 Display verbose information when linking.
161 :program:`dsymutil` returns 0 if the DWARF debug information was linked
|
| /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 …]
|
| /external/llvm-project/clang/include/clang/Basic/ |
| D | BuiltinsBPF.def | 4 // See https://llvm.org/LICENSE.txt for license information.
10 // this file must define the BUILTIN macro to make use of this information.
20 // Get record field information.
26 // Get type information.
|
| /external/autotest/frontend/client/src/autotest/moblab/rpc/ |
| D | MoblabRpcHelper.java | 205 String information = result.isArray().get(1).isString().stringValue(); in addMoblabDut()
206 callback.onLogActionComplete(didSucceed, information); in addMoblabDut()
225 String information = result.isArray().get(1).isString().stringValue(); in removeMoblabDut()
226 callback.onLogActionComplete(didSucceed, information); in removeMoblabDut()
247 String information = result.isArray().get(1).isString().stringValue(); in addMoblabLabel()
248 callback.onLogActionComplete(didSucceed, information); in addMoblabLabel()
269 String information = result.isArray().get(1).isString().stringValue(); in removeMoblabLabel()
270 callback.onLogActionComplete(didSucceed, information); in removeMoblabLabel()
293 String information = result.isArray().get(1).isString().stringValue(); in setMoblabAttribute()
294 callback.onLogActionComplete(didSucceed, information); in setMoblabAttribute()
[all …]
|
| /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/e2fsprogs/tests/f_opt_extent_ext3/ |
| D | expect | 10 Writing superblocks and filesystem accounting information: done
16 Pass 5: Checking group summary information
24 Pass 5: Checking group summary information
42 Pass 5: Checking group summary information
|
| /external/e2fsprogs/tests/f_opt_extent/ |
| D | expect | 10 Writing superblocks and filesystem accounting information: done
16 Pass 5: Checking group summary information
24 Pass 5: Checking group summary information
53 Pass 5: Checking group summary information
|
| /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/grpc-grpc/src/core/tsi/test_creds/ |
| D | README | 12 When prompted for certificate information, everything is default except the
23 When prompted for certificate information, everything is default.
33 When prompted for certificate information, everything is default except the
46 When prompted for certificate information, everything is default except the
59 When prompted for certificate information, everything is default except the
|
| /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-project/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 …]
|
| /external/llvm-project/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/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
48 --static-libs static libcurl library linking information
49 --version output version information
50 --vernum output the version information as a number (hexadecimal)
|
| /external/e2fsprogs/tests/j_short_uncommitted_trans_mcsum_64bit/ |
| D | expect | 8 Writing superblocks and filesystem accounting information: done
14 Pass 5: Checking group summary information
26 Pass 5: Checking group summary information
|
| /external/e2fsprogs/tests/j_short_uncommitted_trans/ |
| D | expect | 8 Writing superblocks and filesystem accounting information: done
14 Pass 5: Checking group summary information
24 Pass 5: Checking group summary information
|
| /external/llvm-project/llvm/test/CodeGen/X86/ |
| D | stackmap-liveness.ll | 30 ; StackMap 1 (no liveness information available)
42 ; StackMap 1 (patchpoint liveness information enabled)
63 ; StackMap 2 (no liveness information available)
75 ; StackMap 2 (patchpoint liveness information enabled)
109 ; StackMap 3 (no liveness information available)
121 ; StackMap 3 (patchpoint liveness information enabled)
148 ; StackMap 4 (patchpoint liveness information enabled)
160 ; StackMap 5 (patchpoint liveness information enabled)
|