[profiler] Fix reachability in eager logging test
Use a local context and compilation cache clearing to trigger code deletion in ClearUnusedWithEagerLogging, rather than relying on bytecode flushing. This allows the test to succeed with non-flushable native-context-independent code, like Sparkplug baseline code. Bug: v8:11420 Change-Id: Id6e3626b6245b4308d95aa3995a8fb2ee53684f7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2786851Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/master@{#73663}
Showing
Please
register
or
sign in
to comment