diff options
| author | 2019-05-02 17:35:02 -0700 | |
|---|---|---|
| committer | 2019-05-03 19:56:27 +0000 | |
| commit | c8c7e0659a76a951f3ab110ed9b7f37777448d36 (patch) | |
| tree | 8a77fac99879f781d3c4eeaa8c79b3d9eb7bbc13 /compiler/optimizing/optimizing_compiler.h | |
| parent | 765b2a04576f4e985a88165456f5ee55cdfe56b8 (diff) | |
Correctly handle thread deopt with thread-specific JVMTI events
We were incorrectly treating some JVMTI events as still requiring
global deopt even though that requirment had been lifted. This meant
that if one sets thread-specific event notification requests on
multiple threads only some of them will actually be deoptimized. This
could cause events to be missed if the relevant methods/threads had
been jitted.
Test: ./test.py --host --jit-on-first-use
Test: ./test.py
Bug: 131865028
Change-Id: Ib196faa635e61262eea7ccc576dc0d700b3e7eff
Diffstat (limited to 'compiler/optimizing/optimizing_compiler.h')
0 files changed, 0 insertions, 0 deletions