diff options
| author | 2021-05-26 16:40:20 +0100 | |
|---|---|---|
| committer | 2021-05-28 00:31:54 +0000 | |
| commit | 654f01cd509ca11eae22177d4e764f1241fb3a53 (patch) | |
| tree | d17db438be0691a5e4e6b4721b670530e336690e /compiler/optimizing/instruction_simplifier_test.cc | |
| parent | 028c7efaf7321a1e253fb4d9dcc5d85e8a9e6d68 (diff) | |
Fix lock visiting for synchronized native methods.
The `GetGenericJniSynchronizationObject()` function was used
in the wrong context. As documented, it can be used only for
a method with a GenericJni frame and also on the top of the
stack. When visiting locks, we can have a non-GenericJni
method frame as well as a method deeper in the stack.
Replace the wrong use with specialized code.
Test: Added regression test to 178-app-image-native-methods
Test: testrunner.py --host --debug --ndebug
Bug: 172332525
Bug: 189235039
Change-Id: Ia26f0b980c04a766e31b1588a1c011bcf46c90d8
Diffstat (limited to 'compiler/optimizing/instruction_simplifier_test.cc')
0 files changed, 0 insertions, 0 deletions