Searched refs:it (Results 1 – 25 of 159) sorted by relevance
1234567
| /dalvik/vm/mterp/mips/ |
| D | OP_INVOKE_OBJECT_INIT_RANGE.S | 23 bnez a0, common_exceptionThrown # yes, handle it
31 GOTO_OPCODE(t0) # execute it
44 GOTO_OPCODE_BASE(a1, t0) # execute it
|
| D | OP_NOP.S | 4 GOTO_OPCODE(t0) # execute it
|
| D | OP_THROW.S | 12 # bypass dvmSetException, just store it
|
| /dalvik/vm/mterp/armv5te/ |
| D | OP_INVOKE_OBJECT_INIT_RANGE.S | 23 GOTO_OPCODE(ip) @ execute it
31 bne common_exceptionThrown @ yes, handle it
44 GOTO_OPCODE_BASE(r1,ip) @ execute it
|
| D | OP_NOP.S | 4 GOTO_OPCODE(ip) @ execute it
|
| D | OP_THROW.S | 12 @ bypass dvmSetException, just store it
|
| /dalvik/vm/jdwp/ |
| D | README.txt | 5 behind this is that it's better to leave a call unimplemented than have
12 though, it's difficult to keep things "generic".
|
| /dalvik/dx/tests/110-dex-preserve-this/ |
| D | info.txt | 3 debuggers will get confused if "this" is reused, and it arguably
9 version, so it is possible for this test to spuriously fail if other
|
| /dalvik/tests/063-process-manager/ |
| D | info.txt | 1 Test that spawning a child process and then reaping it (a) works and (b)
|
| /dalvik/vm/mterp/ |
| D | NOTES.txt | 21 at a time, but since that only happens in the "debug" interpreter it's not
22 necessary for authors of platform-specific code to worry about it.)
59 If it's not possible to obey this rule, then we need to track the value
61 to accomplish this is to store it in the interpreted stack where the GC
62 can find it, and use a live-precise GC to ignore the value.
66 when it's no longer needed can be awkward.
|
| /dalvik/dx/tests/030-minimal-jasmin/ |
| D | info.txt | 2 file and then dumping it. It doesn't test any features in particular.
|
| /dalvik/dx/tests/118-find-usages/ |
| D | info.txt | 1 Creates a .dex file and runs find usages on it to find references and declarations.
|
| /dalvik/tests/080-oom-throw/ |
| D | info.txt | 2 the JIT'ed code handles OOM exception correctly since it cannot fall back to
|
| /dalvik/vm/mterp/x86/ |
| D | OP_CONST_WIDE_32.S | 4 SPILL(rIBASE) # save rIBASE (cltd trashes it)
|
| D | OP_CONST_WIDE_16.S | 4 SPILL(rIBASE) # preserve rIBASE (cltd trashes it)
|
| /dalvik/tools/dexdeps/ |
| D | README.txt | 5 not define. When combined with a list of public APIs, it can be used to
6 determine whether an APK is accessing fields and calling methods that it
|
| /dalvik/dx/tests/091-ssa-const-collector/ |
| D | info.txt | 4 version, so it is possible for this test to spuriously fail if other
|
| /dalvik/dx/tests/098-dex-jsr-ret-throw/ |
| D | info.txt | 3 such a way that it caused the frame merge and subroutine inliner
|
| /dalvik/dx/tests/111-use-null-as-array/ |
| D | info.txt | 11 throw a NullPointerException if ever executed). However, it happens
17 version, so it is possible for this test to spuriously fail if other
|
| /dalvik/dx/tests/003-magic-version-access/ |
| D | info.txt | 3 dumping it.
|
| /dalvik/dx/tests/109-int-branch/ |
| D | info.txt | 5 version, so it is possible for this test to spuriously fail if other
|
| /dalvik/dx/tests/007-no-superclass/ |
| D | info.txt | 3 dumping it.
|
| /dalvik/dx/tests/092-ssa-cfg-edge-cases/ |
| D | info.txt | 4 version, so it is possible for this test to spuriously fail if other
|
| /dalvik/dx/tests/006-interfaces/ |
| D | info.txt | 3 dumping it.
|
| /dalvik/dx/tests/122-switch-with-high-register/ |
| D | info.txt | 5 version, so it is possible for this test to spuriously fail if other
|
1234567