History log of /dalvik/tests/083-jit-regressions/src/Main.java
Revision Date Author Comments
ac3da004fe02e855e2444ce76abf13f12e2e0050 07-Jun-2012 Mattias Petersson <mattias.petersson@sonymobile.com> Missing zero-checks in JIT compiler

Zero-checks were not generated by the JIT compiler for
some instructions. This caused crashes instead of
the expected ArithmeticException.

Change-Id: Ic8041741a7cccc1bd6b8c3c0723ba55a55af856b
232c385b9ece322d677a48947ab1e052c1e2427c 18-Jan-2012 Ben Cheng <bccheng@google.com> Bug fix for control-flow construction involving nested loops.

Bug: 5884080
Change-Id: Ic2f42abae3e71f9c0729984902396f92902184a3
f36ff048fa354bcc7597a187002728106a8b9346 18-Jan-2012 Ben Cheng <bccheng@google.com> Bug fix for control-flow construction involving nested loops.

Bug: 5884080
Change-Id: Ic2f42abae3e71f9c0729984902396f92902184a3
60a6fa031b0e84b508b9795bc826a121e34d5e33 12-Mar-2010 Ben Cheng <bccheng@android.com> Add a JIT unit test for ArrayStoreException in APUT_OBJECT.

Bug: 2487514

tests> ./run-test --fast 083-jit-regressions
/home/bccheng/local/master-git/dalvik/tests/083-jit-regressions: running...
/home/bccheng/local/master-git/dalvik/tests/083-jit-regressions: succeeded!

tests> ./run-test --jit 083-jit-regressions
/home/bccheng/local/master-git/dalvik/tests/083-jit-regressions: running...
/home/bccheng/local/master-git/dalvik/tests/083-jit-regressions: FAILED!

--- expected.txt 2010-03-12 13:45:13.000000000 -0800
+++ output.txt 2010-03-12 14:51:38.000000000 -0800
@@ -1,3 +1,3 @@
b2296099 passes
b2302318 passes
-b2487514 passes
+b2487514 fails: catchCount is 17 (expecting 1000)

Change-Id: I6651a3e0945f96bbb9e0c0af13f2c322b82d0cb0
11aa1bb56f84e83d49a4b9e7b2cb90fd9ab094b0 11-Dec-2009 Bill Buzbee <buzbee@google.com> Jit: Fix 083-jit-regressions test to omit non-deterministic output
2ce8a6c8c11432338cf0cbca8f462e2cf7da1843 04-Dec-2009 Bill Buzbee <buzbee@google.com> Jit: Fix for [Issue 2302318] Crash during spin-on-suspend testing

This was an amusing bug: the test case simulated a daemon by falling
into an empty loop-forever. The trace selector treats unconditional
branches as NOPs, and proceeded to repeatedly add the same "branch to self"
instruction to the trace until it reached max trace size. The compiler
got confused, and died.
0e605279abe713cb54cac3b8eec90d674b6766ce 01-Dec-2009 Bill Buzbee <buzbee@google.com> Jit: shift bug fix - 2296099