/ndk/sources/host-tools/make-3.81/ |
D | strcache.c | 60 struct strcache *best = NULL; in add_string() local 74 if (sp->bytesfree > len && (!best || best->bytesfree > sp->bytesfree)) in add_string() 75 best = sp; in add_string() 78 if (!best) in add_string() 79 best = new_cache(); in add_string() 81 assert (best->bytesfree > len); in add_string() 84 res = best->end; in add_string() 85 memcpy (best->end, str, len); in add_string() 86 best->end += len; in add_string() 87 *(best->end++) = '\0'; in add_string() [all …]
|
D | README.customs | 20 please see the pmake and Customs documentation for details. The best
|
D | Makefile.in | 144 GZIP_ENV = --best
|
D | COPYING | 286 possible use to the public, the best way to achieve this is to make it
|
/ndk/sources/host-tools/sed-4.2.1/sed/ |
D | fmt.c | 438 register COST wcost, best; in fmt_paragraph() local 447 best = MAXCOST; in fmt_paragraph() 463 if (wcost < best) in fmt_paragraph() 465 best = wcost; in fmt_paragraph() 472 start->best_cost = best + base_cost (start); in fmt_paragraph()
|
/ndk/sources/host-tools/make-3.81/tests/scripts/variables/ |
D | negative | 7 # reported using the best filename/lineno info
|
/ndk/sources/third_party/googletest/googletest/include/gtest/internal/ |
D | gtest-type-util.h.pump | 150 // Our solution is to combine the best part of the two approaches: a 248 // Our solution is to combine the best part of the two approaches: a
|
/ndk/docs/text/ |
D | CPU-X86.text | 81 ### Porting considerations and best known methods are:
|
D | CPU-ARCH-ABIS.text | 365 To achieve the best performance for your NDK component, you should compile 400 This mechanism ensures that the best machine code for the target
|
/ndk/sources/host-tools/sed-4.2.1/ |
D | Makefile.in | 118 GZIP_ENV = --best
|
D | COPYING | 627 possible use to the public, the best way to achieve this is to make it
|
/ndk/sources/host-tools/sed-4.2.1/testsuite/ |
D | BOOST.tests | 277 ; strictly speaking this is at best ambiguous, at worst wrong, this is what most
|
/ndk/sources/third_party/googletest/googletest/ |
D | README | 26 Linux, Windows, Mac OS X, and Cygwin. We will also make our best
|
/ndk/sources/host-tools/make-3.81/tests/ |
D | COPYING | 285 possible use to the public, the best way to achieve this is to make it
|
/ndk/tests/device/test-stlport_shared-exception/ |
D | COPYING | 285 possible use to the public, the best way to achieve this is to make it
|
/ndk/tests/build/test-stlport_static-exception-force-rebuild/ |
D | COPYING | 285 possible use to the public, the best way to achieve this is to make it
|
/ndk/tests/build/lambda-defarg3/ |
D | COPYING | 285 possible use to the public, the best way to achieve this is to make it
|
/ndk/build/tools/toolchain-licenses/ |
D | COPYING | 285 possible use to the public, the best way to achieve this is to make it
|
/ndk/tests/abcc/jni/mman-win32/ |
D | LICENSE.TXT | 285 possible use to the public, the best way to achieve this is to make it
|
/ndk/tests/device/test-stlport_static-exception/ |
D | COPYING | 285 possible use to the public, the best way to achieve this is to make it
|
/ndk/sources/host-tools/make-3.81/doc/ |
D | make-stds.texi | 120 @file{foo.1} is best written as: 820 Generate any Info files needed. The best way to write the rules is as
|
/ndk/sources/host-tools/make-3.81/config/ |
D | texinfo.tex | 1371 % their "best" equivalent, based on the @documentencoding. Right 2119 % be smaller yet, but lllsize is the best we can do for now. 3397 % control sequences and just writes whatever the best ASCII sort string 3459 % Of course this is not nearly correct, but it is the best we can do for now. 3710 % Do our best not to break after the initial. 4291 % 3) Likewise, headings look best if no \parindent is used, and 6115 % are best written with fairly long node names, containing hyphens, this 6548 % float "here". But it seemed the best name for the future.
|
/ndk/sources/host-tools/sed-4.2.1/build-aux/ |
D | texinfo.tex | 1546 % their "best" equivalent, based on the @documentencoding. Right 2974 % be smaller yet, but lllsize is the best we can do for now. 3433 % right away at the @itemize. It's not the best error message in the 4347 % control sequences and just writes whatever the best ASCII sort string 4424 % Of course this is not nearly correct, but it is the best we can do for now. 4679 % Do our best not to break after the initial. 5293 % 3) Likewise, headings look best if no \parindent is used, and 7276 % are best written with fairly long node names, containing hyphens, this 7723 % float "here". But it seemed the best name for the future.
|
/ndk/sources/host-tools/ndk-stack/binutils/ |
D | COPYING3 | 626 possible use to the public, the best way to achieve this is to make it
|
/ndk/sources/host-tools/gdb-pretty-printers/stlport/gppfs-0.2/ |
D | COPYING | 627 possible use to the public, the best way to achieve this is to make it
|