diff options
| author | 2022-12-09 16:46:16 +0000 | |
|---|---|---|
| committer | 2023-01-03 11:32:16 +0000 | |
| commit | 890b19bd625be5d0e4a876e3eb11b8b893fb0c13 (patch) | |
| tree | 0162d953a9e091dc746efcb2889f2e0354bb51db /runtime/string_builder_append.cc | |
| parent | aa124735bb61071f9036e1140355c4d1a088b1a9 (diff) | |
Don't use instrumentation stubs for supporting entry / exit hooks
We want to deprecate instrumentation stubs to reduce the complexity of
the instrumentation support. If the runtime has started off as
debuggable runtime we start with interpreter / GenericJniStubs and
generate JIT code with instrumentation support for hot methods.
For non-debuggable runtimes that need instrumentation support, we switch
the entrypoints to interpreter / GenericJniStubs and discard all JITed
code. Similar to debuggable runtime we generate JIT code with
instrumentation support. For the methods that are already executing on
the stack we may miss calling entry / exit hooks. This is a best effort
anyway and it is OK to miss them.
Bug: 206029744
Test: art/test.py
Change-Id: Ic422d4e9790ebf86a360a3285350dd692cfd6b43
Diffstat (limited to 'runtime/string_builder_append.cc')
0 files changed, 0 insertions, 0 deletions