diff options
| author | 2022-08-25 14:03:26 +0100 | |
|---|---|---|
| committer | 2022-09-05 12:24:25 +0100 | |
| commit | 28451dc19280f0c1991f9af6f3c087f3ec08de79 (patch) | |
| tree | 2e4123d8648c147618d2b0bc4761277a9e3a073f /compiler/optimizing/code_sinking.cc | |
| parent | 94383b4038970838ded1f0a482f16d8b612a4701 (diff) | |
Fix `ClassLinker::AppendToBootClassPath` usages.
Both `Runtime` and `ClassLinker` maintain information about
bootclasspath, and they should keep in sync. However, some test and
jvmti code dynamically add elements to bootclasspath by only calling
`ClassLinker::AppendToBootClassPath`. This can break oat file validation
because the validation is based on the bootclasspath that `Runtime`
maintains. This CL fixes them by adding elements through `Runtime`,
which updates both itself and `ClassLinker`.
Bug: 243128839
Test: art/test.py -b -r --host --debug --cdex-fast --optimizing \
--redefine-stress --debuggable
Test: art/test.py -b -r --host --debug
Test: art/test.py -b -g --host --debug
Change-Id: I92a2c039080abf30455f375628ec9351c35e1897
Diffstat (limited to 'compiler/optimizing/code_sinking.cc')
0 files changed, 0 insertions, 0 deletions