diff options
| author | 2023-10-06 16:22:15 +0000 | |
|---|---|---|
| committer | 2023-10-11 10:15:29 +0000 | |
| commit | 6f563af0994a422d4829a295841f8c0641293afb (patch) | |
| tree | 3c80a57f8a59376720bfa3872d8f17b26e3d56af /compiler/optimizing/optimizing_compiler.cc | |
| parent | 6f2189f2bcf65c58b1bc79b33eca715df35a3d92 (diff) | |
Update entrypoints after switching the runtime to non-debuggable
When detaching a debugger or stopping tracing in non-debuggable
runtimes, we switch back to non-debuggable mode. We used to switch to
non-debuggable mode after updating the entrypoints of methods. This
meant we don't use AOT code for these methods. For this to work
correctly we should
1. Update instrumentation level
2. Switch runtime if possible
3. Update entry points.
Since this order is important, we no longer expose MaybeSwitchRuntime as
a public member. Instead we pass a parameter that says if we should try
and switch the runtime to non-debuggable.
Bug: 303686344
Test: art/test.py
Change-Id: Id655ca50964ed10072ff5bfc3e565c08ecb9987b
Diffstat (limited to 'compiler/optimizing/optimizing_compiler.cc')
0 files changed, 0 insertions, 0 deletions