diff options
| author | 2023-05-15 13:13:40 +0000 | |
|---|---|---|
| committer | 2023-05-16 10:52:04 +0000 | |
| commit | 94d58fe6c99f83037e3b1587bf90c84c154f045a (patch) | |
| tree | 9ad7710bad1c1dfb7e90eab7671287d4c0127ba0 /compiler/optimizing/code_generator.h | |
| parent | 1d92d827f6b4ea6bde87b55bfb1715174f9069b3 (diff) | |
Always use debuggable from compiler options when JITing
We use two slightly different ways to check if we need to generate
debuggable support for JITed code or not. We usually check for
debuggable flag from the compiler options but also use
Runtime::IsJavaDebuggable in some places. While these two usually match,
it is possible to set compiler options independent of the runtime
debuggability. So always use debuggable from compiler options when
making decisions on JITed code.
Bug: 282239094
Test: art/test.py
Change-Id: Ia47f146834e0ae1aec2c5694d3d7a468be51435f
Diffstat (limited to 'compiler/optimizing/code_generator.h')
0 files changed, 0 insertions, 0 deletions