Searched
full:optimization (Results
651 -
675 of
2421) sorted by null
<<21222324252627282930>>
/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/man/man1/ |
arm-eabi-gcov.1 | 154 optimization efforts will best affect your code. You can also use 171 \&\fBgcov\fR helps you determine where to work on optimization. 181 You should compile your code without optimization if you plan to use 182 \&\fBgcov\fR because the optimization, by combining some lines of code 553 .Sh "Using \fBgcov\fP with \s-1GCC\s0 Optimization" 554 .IX Subsection "Using gcov with GCC Optimization" 559 in your program was executed, you should not compile with optimization 575 optimization: 584 The output shows that this block of code, combined by optimization,
|
/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/man/man1/ |
arm-eabi-gcov.1 | 154 optimization efforts will best affect your code. You can also use 171 \&\fBgcov\fR helps you determine where to work on optimization. 181 You should compile your code without optimization if you plan to use 182 \&\fBgcov\fR because the optimization, by combining some lines of code 553 .Sh "Using \fBgcov\fP with \s-1GCC\s0 Optimization" 554 .IX Subsection "Using gcov with GCC Optimization" 559 in your program was executed, you should not compile with optimization 575 optimization: 584 The output shows that this block of code, combined by optimization,
|
/prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/man/man1/ |
arm-linux-androideabi-gcov.1 | 155 optimization efforts will best affect your code. You can also use 172 \&\fBgcov\fR helps you determine where to work on optimization. 182 You should compile your code without optimization if you plan to use 183 \&\fBgcov\fR because the optimization, by combining some lines of code 568 .SS "Using \fBgcov\fP with \s-1GCC\s0 Optimization" 569 .IX Subsection "Using gcov with GCC Optimization" 574 in your program was executed, you should not compile with optimization 590 optimization: 599 The output shows that this block of code, combined by optimization,
|
/prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu-4.2.1/man/man1/ |
i686-unknown-linux-gnu-gcov.1 | 153 optimization efforts will best affect your code. You can also use 170 \&\fBgcov\fR helps you determine where to work on optimization. 180 You should compile your code without optimization if you plan to use 181 \&\fBgcov\fR because the optimization, by combining some lines of code 543 .Sh "Using \fBgcov\fP with \s-1GCC\s0 Optimization" 544 .IX Subsection "Using gcov with GCC Optimization" 549 in your program was executed, you should not compile with optimization 565 optimization: 574 The output shows that this block of code, combined by optimization,
|
/external/bluetooth/bluez/ |
acinclude.m4 | 215 AC_ARG_ENABLE(optimization, AC_HELP_STRING([--disable-optimization], [disable code optimization]), [
|
/external/icu4c/common/ |
ucnv_lmb.c | 209 translations even faster,sometimes the optimization group byte can be dropped 211 group byte that is dropped is called the 'optimization group'. 219 optimization group as part of the name of the converter (LMBCS-1, LMBCS-2, 228 keeps a mapping between optimization groups and IBM character sets, so that 231 /* As you can see, even though any byte below 0x20 could be an optimization 570 we use, the optimization group, and the group (if any) that matches the 572 optimization groups. To avoid typos & to avoid boring the reader, we 619 optimization group. So, we put the common stuff into a worker function, 871 A) The optimization group [all...] |
/external/llvm/tools/lli/ |
lli.cpp | 63 // Determine optimization level. 66 cl::desc("Optimization level. [-O0, -O1, -O2, or -O3] " 199 errs() << argv[0] << ": invalid optimization level.\n";
|
/external/oprofile/ |
configure.in | 191 AC_ARG_ENABLE(optimization, 192 [ --disable-optimization disable optimization flags (default is enabled)],
|
/external/pcre/doc/html/ |
pcreperform.html | 121 optimization, because the . metacharacter does not then match a newline, and if 154 An optimization catches some of the more simple cases such as 161 following literal this optimization cannot be used. You can see the difference
|
/ndk/build/core/ |
add-application.mk | 192 $(call ndk_log,Selecting optimization mode through Application.mk: $(APP_OPTIM)) 195 $(call ndk_log,Selecting debug optimization mode (app is debuggable)) 198 $(call ndk_log,Selecting release optimization mode (app is not debuggable))
|
/bionic/libc/kernel/tools/ |
defaults.py | 26 # undefined during optimization
|
/bionic/libm/src/ |
k_sin.c | 28 * Callers may do the optimization sin(x) ~ x for tiny x.
|
/dalvik/dexgen/src/com/android/dexgen/rop/code/ |
DexTranslationAdvice.java | 32 /** debug advice for disabling invoke-range optimization */
|
/dalvik/dx/src/com/android/dx/rop/code/ |
DexTranslationAdvice.java | 32 /** debug advice for disabling invoke-range optimization */
|
/dalvik/tests/etc/ |
push-and-run-test-jar | 15 # --no-optimize -- turn off optimization (on by default)
|
/dalvik/vm/ |
DvmDex.h | 79 * Open a partial DEX file. Only useful as part of the optimization process.
|
/dalvik/vm/analysis/ |
DexPrepare.h | 121 * Continue the optimization process on the other side of a fork/exec.
|
/dalvik/vm/compiler/codegen/arm/armv5te-vfp/ |
ArchVariant.cpp | 101 LOGE("Unknown target optimization hint key: %d",key);
|
/external/bluetooth/glib/build/win32/vs8/ |
glib-genmarshal.vcproj | 42 Optimization="0"
|
gspawn-win32-helper-console.vcproj | 42 Optimization="0"
|
gspawn-win32-helper.vcproj | 42 Optimization="0"
|
gthread.vcproj | 42 Optimization="0"
|
/external/chromium/sdch/open-vcdiff/vsprojects/addrcache_test/ |
addrcache_test.vcproj | 43 Optimization="0"
|
/external/chromium/sdch/open-vcdiff/vsprojects/blockhash_test/ |
blockhash_test.vcproj | 43 Optimization="0"
|
/external/chromium/sdch/open-vcdiff/vsprojects/codetable_test/ |
codetable_test.vcproj | 43 Optimization="0"
|
Completed in 429 milliseconds
<<21222324252627282930>>