| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Backport from dalvik-dev, due to customer demand.
Bug: http://code.google.com/p/android/issues/detail?id=41196
Change-Id: I53ef57e54983f2173546463ac78e265ff5dd3284
|
| |
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
Two threads were waiting for initialization of a class to complete.
There was nothing encouraging one thread to resume execution first,
but on single-core devices it always worked out the same way.
Bug 3366697
Change-Id: I29430d398dfbd9509d7db2b7db2800d340b29d19
|
| |
|
|
| |
Change-Id: I1e3d103a7b932ef21acedb6438c0f26b315df28f
|
|
|
This tests for races during init, and correctness after an exception is
thrown partway through.
For bug 2655384.
Change-Id: I837ec435d1655e49b8b39f4129bd321857172870
|