| aec9c8f142ad839883ae3de7383456a08823a282 |
|
01-Feb-2012 |
Elliott Hughes <enh@google.com> |
Updates to the VM tests.
Bug: http://code.google.com/p/android/issues/detail?id=21599
Bug: http://code.google.com/p/android/issues/detail?id=21597
Change-Id: I9c6d67cd18943eb6fa68104f0ec2fbec5ea9e0ec
|
| a5a184892e60a89b564ca7c74e50b2ecb27d9f80 |
|
20-Jan-2012 |
Andy McFadden <fadden@android.com> |
Update and extend Dalvik tests
029 - exercise setDefaultAssertionStatus
031 - enable some tests that were disabled back when our generics
support didn't exist. Added new FancyClass test.
034 - print success/fail rather than matching exact exception text
038 - (same as 034)
042 - added new test for bug 5861201, currently disabled
045 - added a bunch of new tests, including one that fails
046 - added new tests, including some for bug 5861201 (the latter
are disabled)
068 - loadClass() wants class names with dots, not slashes
086 - (same as 068)
087 - (same as 068)
092 - new test, exercises some locale-specific classes
093 - new test, exercises object serialization
094 - new test, exercises regex code
Test 045 now fails, because it's exercising a feature that should
work but doesn't. All others pass.
Change-Id: I6481bfa88681c4ac8af629cb60797b2708bdeba4
|
| 060f9a6f626edfbb3ca1af632de69c6c87b392b0 |
|
11-Sep-2010 |
Andy McFadden <fadden@android.com> |
Added a barrier to final field updates.
When deserializing an object, code can write to final fields. The JMM
requires that we give final fields written this way the same treatment
as we would final fields written directly in a constructor.
This adds memory barriers to the two reflection field-set handlers
when the field in question is marked "final".
Also, added a final field update to test 046.
Bug 2965743.
Change-Id: I5ea3cb49e04d932a655740058b847dcb8712e041
|
| 7365493ad8d360c1dcf9cd8b6eee62747af01cae |
|
09-Jun-2010 |
Carl Shapiro <cshapiro@google.com> |
Remove repeated newlines at the end of files.
Change-Id: I1e3d103a7b932ef21acedb6438c0f26b315df28f
|
| 798e74341e03edf2c30728a141dc6af7a89f9e1f |
|
16-Jun-2009 |
Andy McFadden <fadden@android.com> |
Don't init class during reflection signature scan.
Do not merge to master -- this is 57ea16e8 from there.
When processing Class.getDeclaredMethods() we create Method objects.
These have arrays of classes that indicate the method parameter types.
While generating the array we were initializing the classes we found,
which isn't necessary and led to some unpleasantness described in
external bug 3005.
|
| 57ea16e87e319bf71176dd8e8d12abe84f13d2e6 |
|
16-Jun-2009 |
Andy McFadden <fadden@android.com> |
Don't init class during reflection signature scan.
When processing Class.getDeclaredMethods() we create Method objects.
These have arrays of classes that indicate the method parameter types.
While generating the array we were initializing the classes we found,
which isn't necessary and led to some unpleasantness described in
external bug 3005.
|
| f6c387128427e121477c1b32ad35cdcaa5101ba3 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
|
| f72d5de56a522ac3be03873bdde26f23a5eeeb3c |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
|
| 2ad60cfc28e14ee8f0bb038720836a4696c478ad |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
|