/ndk/build/core/ |
setup-app.mk | 42 # which platform/abi/toolchain are we going to use? 68 # This ensures that if the build fails, you're not going to mistakenly 70 # you're not going to leave a stale shared library for the old one.
|
add-application.mk | 91 # If not, we're going to use the max supported platform value.
|
setup-toolchain.mk | 24 # NOTE: If NDK_TOOLCHAIN is defined, we're going to use it.
|
init.mk | 398 # we're going to find the maximum platform number of the form android-<number>
|
/dalvik/vm/mterp/x86/ |
OP_CHECK_CAST.S | 58 * going to have to recreate some data.
|
OP_CHECK_CAST_JUMBO.S | 58 * going to have to recreate some data.
|
footer.S | 430 cmpw $$0, offThread_subMode(%ecx) # Anything special going on?
|
/external/webkit/Source/WebCore/manual-tests/inspector-wrappers/ |
inspector-wrappers-test-utils.js | 18 var url = prompt("Test failed. To prove it, I'm going " +
|
/dalvik/vm/mterp/armv5te/ |
OP_EXECUTE_INLINE.S | 20 ands r2, #kSubModeDebugProfile @ Any going on?
|
OP_EXECUTE_INLINE_RANGE.S | 18 ands r2, #kSubModeDebugProfile @ Any going on?
|
/development/build/ |
Android.mk | 51 # code is never going to be run anywhere, so just make a copy of the file.
|
/external/chromium/chrome/browser/resources/file_manager/js/ |
util.js | 107 // Copy the params array, since we're going to destroy it.
|
/external/webkit/LayoutTests/dom/xhtml/level3/core/ |
documentnormalizedocument11.js | 80 The normalizeDocument method method acts as if the document was going through a save
|
documentnormalizedocument09.js | 109 The normalizeDocument method method acts as if the document was going through a save
|
documentnormalizedocument10.js | 79 The normalizeDocument method method acts as if the document was going through a save
|
documentnormalizedocument12.js | 111 The normalizeDocument method method acts as if the document was going through a save
|
/sdk/sdkmanager/app/etc/ |
android.bat | 50 rem We're now going to create a temp dir to hold all the Jar files needed
|
/external/chromium/chrome/browser/resources/net_internals/ |
logviewpainter.js | 247 // 0 is always going to be false. 352 // Don't prefix with '+' if we are going to collapse the END event.
|
dataview.js | 90 * Called when either a log file is loaded or when going back to actively
|
/external/libvpx/vp8/common/arm/armv6/ |
recon_v6.asm | 34 ; going out.
|
/external/blktrace/doc/ |
blktrace.tex | 65 As noted above, the kernel patch along with the blktrace and blkparse utilities are stored in a git repository. One simple way to get going would be: 138 Now to simply watch what is going on for a specific disk (to stop the 200 can also show SCSI commands going in and out of the queue as submitted 390 -k & --kill & Kill on-going trace \\ \hline [all...] |
/build/core/ |
main.mk | 361 # These targets are going to delete stuff, don't bother including 362 # the whole directory tree if that's all we're going to do 655 # to build the host tools, but nothing that's going to be installed
|
/external/clang/tools/scan-build/ |
scan-build | 954 -k - Add a "keep on going" option to the specified build command. 955 --keep-going This option currently supports make and xcodebuild. [all...] |
/external/v8/src/ |
liveedit-debugger.js | 98 // Recursively collects all newly compiled functions that are going into 193 // Link to an actual script all the functions that we are going to use. [all...] |
/external/blktrace/btt/doc/ |
btt.tex | 68 The simple pipeline to get going with \texttt{btt} is to perform the 365 (if ever?) going to be associated with the process which submitted 588 and blue dots are somewhat similar below about 192 blocks per IO going [all...] |