• Clemens Backes's avatar
    [wasm][debug] Fix tier down for multiple isolates · 902f48bd
    Clemens Backes authored
    If multiple isolates are using the same module, we need to keep it
    tiered down as long as any isolate still has a debugger open.
    Also, we cannot short-cut the {NativeModule::TierDown} method, since the
    previously triggered tier down might not have finished yet.
    For now, each isolate starts an independent tier down (i.e. a full
    recompilation). We could optimize this later by skipping functions that
    are already tiered down, or are already scheduled for tier down, but we
    still need to wait for tier-down to finish on each isolate.
    
    R=thibaudm@chromium.org
    
    Bug: v8:10359
    Change-Id: I7ea6a6f5d3977e48718ac5bc94f9831541f6173f
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190758
    Commit-Queue: Clemens Backes <clemensb@chromium.org>
    Reviewed-by: 's avatarThibaud Michaud <thibaudm@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#67716}
    902f48bd
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
debugging Loading commit data...
fuzzer Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
test262 Loading commit data...
torque Loading commit data...
unittests Loading commit data...
wasm-api-tests Loading commit data...
wasm-js Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
OWNERS Loading commit data...