Searched refs:described (Results 1 – 25 of 174) sorted by relevance
1234567
/external/v8/tools/visual_studio/ |
D | README.txt | 34 described above. The location of the output directory used are defined in 57 solution with v8_base, v8, v8_mksnapshot and v8_snapshot set up as described 58 solution with v8_base, v8, v8_mksnapshot and v8_snapshot set up as described 63 dependencies configured as described above.
|
/external/openssl/crypto/dsa/ |
D | fips186a.txt | 13 generation standard described in appendix 2 using the 160-bit SEED: 19 x was generated by the algorithm described in appendix 3, section 3.1, using 31 k was generated by the algorithm described in appendix 3, section 3.2, using
|
/external/libvpx/ |
D | keywords.dox | 5 "OPTIONAL" in this document are to be interpreted as described in 34 before implementing any behavior described with this label.
|
/external/llvm/test/TableGen/ |
D | TargetInstrInfo.td | 74 // described here. Eventually we can do away with this when everything 96 // Two address instructions are described as three-addr instructions, with 122 // can just be described in nested form. This would be the canonical
|
/external/chromium/base/third_party/dynamic_annotations/ |
D | README.chromium | 11 The files are covered under BSD license as described within the files.
|
/external/valgrind/main/coregrind/m_debuginfo/ |
D | debuginfo.c | 2650 XArray* /*UChar*/ described, in format_message() 2663 vg_assert(described); in format_message() 2665 have_descr = VG_(sizeXA)(described) > 0 in format_message() 2666 && *(UChar*)VG_(indexXA)(described,0) != '\0'; in format_message() 2752 (HChar*)(VG_(indexXA)(described,0)) ); in format_message() 2762 (HChar*)(VG_(indexXA)(described,0)) ); in format_message() 2776 (HChar*)(VG_(indexXA)(described,0)) ); in format_message() 2793 (HChar*)(VG_(indexXA)(described,0)) ); in format_message() 2860 (HChar*)(VG_(indexXA)(described,0)) ); in format_message() 2870 (char*)(VG_(indexXA)(described,0)) ); in format_message() [all …]
|
/external/valgrind/main/docs/internals/ |
D | m_syswrap.txt | 9 caveats are described in comments at the top of syswrap-main.c.
|
/external/oprofile/ |
D | README_PACKAGERS | 5 described in: 36 library is built. As with libopagent described above, the install location
|
/external/webkit/Tools/android/flex-2.5.4a/MISC/ |
D | NeXT | 10 Specifically (in addition to what's described in the KBNS item):
|
/external/stlport/stlport/ |
D | complex | 28 // This header declares the template class complex, as described in
|
/external/zlib/projects/ |
D | README.projects | 21 Application Binary Interface (ABI), described in win32/DLL_FAQ.txt.
|
/external/valgrind/main/helgrind/ |
D | README_MSMProp2.txt | 10 machine is different again from any previously described machine. 17 state machine for data race detection. It is described at
|
/external/chromium/sdch/open-vcdiff/ |
D | README | 1 open-vcdiff is an encoder and decoder for the VCDIFF format, as described in
|
/external/iptables/extensions/ |
D | libxt_policy.man | 23 For each policy element that is to be described, one can use one or more of
|
D | libxt_u32.man | 6 The argument amounts to a program in a small language described below. 24 described further below.
|
/external/mesa3d/docs/ |
D | MESA_texture_signed_rgba.spec | 115 and converting back (using the mapping described here). 125 RESOLVED: Same as described in issue 6) of
|
/external/hyphenation/ |
D | COPYING.MPL | 53 which is described in the Source Code notice required by Exhibit A as 155 an additional document offering the additional rights described in 190 the Modification is made available as described in Section 3.2, 216 You may add your name as a Contributor to the notice described in 266 must be included in the LEGAL file described in Section 3.4 and must 302 Developer, Original Code or Contributor in the notice described in 433 by the Initial Developer in the file described in Exhibit A.
|
/external/openssl/crypto/dh/ |
D | generate | 23 Odlyzko described (some variant on a factoring attack which generates
|
/external/expat/win32/ |
D | README.txt | 77 accordingly, as described above
|
/external/dropbear/ |
D | README | 30 NOTE: Dropbear ignores authorized_keys options such as those described in the
|
/external/valgrind/main/none/tests/ |
D | cmdline1.stdout.exp | 33 --suppressions=<filename> suppress errors described in <filename>
|
/external/qemu/docs/ |
D | CHAR-DEVICES.TXT | 75 to the parameters of the '-serial' QEMU option described here: 137 As described above, a CharDriverState "user" is a piece of code that can write
|
/external/chromium/sdch/open-vcdiff/src/gtest/ |
D | README | 34 package (as described below): 41 described below), there are further requirements:
|
/external/bluetooth/glib/ |
D | acinclude.m4 | 47 dnl by setting ac_func_vsnprintf_c99 to yes, as described in the Autoconf manual. 100 dnl by setting ac_func_snprintf_c99 to yes, as described in the Autoconf manual. 131 dnl this by setting ac_func_printf_unix98 to yes, as described in the Autoconf manual.
|
/external/markdown/docs/extensions/ |
D | CodeHilite.txt | 87 behavior will happen as described here.
|
1234567