1. 01 Jun, 2021 1 commit
  2. 19 Jan, 2021 1 commit
    • Clemens Backes's avatar
      [wasm] Fix tier-down test for multiple isolates · 81b3372e
      Clemens Backes authored
      The test was explicitly tiering up or down a module, without respecting
      other isolates. Thus it was failing in multi-isolate mode.
      This CL removes two runtime functions which do not make sense in a
      multi-isolate setting (and were only used in this one test), and
      replaces them with runtime functions that mimic what enabling/disabling
      the debugger domain does: As long as there is at least one isolate which
      needs modules to be tiered down, we keep them tiered down.
      
      R=thibaudm@chromium.org
      
      Bug: v8:10359, v8:10099
      Change-Id: Ia85f4ea29ba6a6bb54aca54a48fadd351121d3eb
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2637231Reviewed-by: 's avatarThibaud Michaud <thibaudm@chromium.org>
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#72164}
      81b3372e
  3. 09 Mar, 2020 1 commit
  4. 06 Feb, 2020 1 commit
    • Z Nguyen-Huu's avatar
      Reland "[wasm] Tierdown wasm module upon "Debugger.enable"" · 1f7861c8
      Z Nguyen-Huu authored
      This is a reland of 410ca4c5
      
      Skip new test for unsupported liftoff architecture.
      Previously, if there is some unsupported liftoff functions, it fall
      through Turbofan but recompilation didn't catch and count it. This CL
      fixes it by using requested_tier on finished units.
      
      Avoid to tier down asm.js.
      Introduce reached recompilation tier to monitor recompilation progress.
      
      Original change's description:
      > [wasm] Tierdown wasm module upon "Debugger.enable"
      >
      > Put a logic in Wasm Engine to tier down all existing modules per isolate
      > when debugger is enabled. This CL does not handle new module added after
      > debugger is enabled yet.
      >
      > Bug: v8:9654
      > Change-Id: I87060f5c416506543fcaf231bff9999d06ba4c0d
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2013692
      > Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com>
      > Reviewed-by: Simon Zünd <szuend@chromium.org>
      > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
      > Reviewed-by: Clemens Backes <clemensb@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#66017}
      
      TBR=szuend@chromium.org,bmeurer@chromium.org
      
      Bug: v8:9654
      Change-Id: I6014ae52d1e04726e64ee9267c5ce559090414d7
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2031744
      Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com>
      Reviewed-by: 's avatarClemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#66164}
      1f7861c8
  5. 22 Jan, 2020 1 commit
    • Z Nguyen-Huu's avatar
      Reland "[wasm] Perform NativeModule tier down in parallel." · 30f94ea4
      Z Nguyen-Huu authored
      This is a reland of faccc95b
      
      Since 1c9bb77d, async jobs use existing
      entry in native module cache and skip recompilation so we need to fix
      the test.
      
      Original change's description:
      > Reland "[wasm] Perform NativeModule tier down in parallel."
      >
      > This is a reland of 3352fcc9
      >
      > Disable stress-opt for test and check recompilation before clearing
      > callbacks.
      >
      > Original change's description:
      > > [wasm] Perform NativeModule tier down in parallel.
      > >
      > > Reuse logic in {CompileNativeModule} function in module-compiler.cc:
      > > initialize parallel compile jobs, then wait for them to finish while
      > > taking part in this compilation.
      > >
      > > Bug: v8:9654
      > > Change-Id: I9974d9f8b516e9faec716a592c7c0ee9c7077d8e
      > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1977041
      > > Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com>
      > > Reviewed-by: Clemens Backes <clemensb@chromium.org>
      > > Cr-Commit-Position: refs/heads/master@{#65763}
      >
      > Bug: v8:9654
      > Change-Id: I8e8830f05e189596207365b7332a2cc25e493e47
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2002945
      > Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com>
      > Reviewed-by: Clemens Backes <clemensb@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#65901}
      
      Bug: v8:9654
      Change-Id: Ia63b86d4275088d93202046bc9823e6202b7991a
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2012986Reviewed-by: 's avatarClemens Backes <clemensb@chromium.org>
      Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com>
      Cr-Commit-Position: refs/heads/master@{#65929}
      30f94ea4
  6. 21 Jan, 2020 2 commits
  7. 15 Jan, 2020 2 commits
  8. 14 Jan, 2020 1 commit
  9. 07 Jan, 2020 1 commit
  10. 30 Jan, 2019 1 commit
  11. 12 Jul, 2018 1 commit