diff options
| author | 2023-11-07 14:44:19 +0000 | |
|---|---|---|
| committer | 2023-11-07 17:13:12 +0000 | |
| commit | 2fdcf22dc6fb24f364008eb612c57582857006a7 (patch) | |
| tree | c081d5f79e098584cfda9d800802073653a25d87 /runtime/javaheapprof/javaheapsampler.h | |
| parent | 9ef4c97403b7ba807effa469897fffdb43fe86d9 (diff) | |
Make it fatal if we cannot initialize private region for jit code cache
We should be able to usually initialize a private region. The rest of
the code assumes that private region has been initialized and that the
code and data mspace have been initialized. If private region couldn't
be initialized we cannot JIT at all. We should be able to initialize
private region always. If we couldn't then it means something else is
not working and we need to fix it. So instead of logging a warning make
it fatal to catch any issues earlier.
Bug: 307441080
Test: art/test.py
Change-Id: I6a090164ffa4b45378400d930a470bbaa56d3535
Diffstat (limited to 'runtime/javaheapprof/javaheapsampler.h')
0 files changed, 0 insertions, 0 deletions