1. 22 Nov, 2018 1 commit
    • Ben L. Titzer's avatar
      [wasm/tools] Add import profiler · 4eb53245
      Ben L. Titzer authored
      Add a profiler for functions imported to WASM instances. This profiler
      is implemented entirely in JavaScript and monkey-patches
      WebAssembly.instantiate() and new WebAssembly.Instance() to instrument
      the imported functions to each instance in order to count their
      invocations and cumulative time.
      
      R=mstarzinger@chromium.org
      
      Bug: v8:8423
      Change-Id: If456355aba07dc69c5500bafbe35fc56b31486af
      Reviewed-on: https://chromium-review.googlesource.com/c/1347488
      Commit-Queue: Ben Titzer <titzer@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#57746}
      4eb53245
  2. 18 Oct, 2018 1 commit
  3. 17 Oct, 2018 2 commits
  4. 25 Jan, 2018 1 commit
  5. 08 Dec, 2017 1 commit
  6. 10 Oct, 2017 1 commit
  7. 21 Jun, 2017 1 commit
  8. 09 Jun, 2017 1 commit
  9. 02 Jun, 2017 1 commit
    • Andreas Haas's avatar
      [wasm] Update the wasm spec tests. · fdb0b7ab
      Andreas Haas authored
      This CL updates the hook for the WebAssembly spec repository, and it
      updates the WebAssembly spec tests. The WebAssembly spec tests have to
      be updated manually with the tools/wasm/update-wasm-spec-tests.sh
      script. Mircea, I saw that you updated the WebAssembly spec repository
      last time. Can you please take a look?
      
      UPDATE: I improved the update script slightly, and there is one
      additional JS API test we fail now and have to fix eventually.
      
      R=mtrofin@chromium.org
      
      Change-Id: I3c0df9cee64d444147db47daa0c1936edf116173
      Reviewed-on: https://chromium-review.googlesource.com/509257Reviewed-by: 's avatarMircea Trofin <mtrofin@chromium.org>
      Commit-Queue: Andreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45692}
      fdb0b7ab
  10. 28 Apr, 2017 1 commit
    • Andreas Haas's avatar
      [wasm] Move the wasm fuzzer corpus to a different directory · 1f629aac
      Andreas Haas authored
      The current test/fuzzer/wasm directory is used for two things:
      1) as the corpus directory for clusterfuzz
      2) to test in v8 that the fuzzer runs correctly.
      
      With the newly added files from the wasm spec tests this directory grew
      quite big and adds unnecessary load on the trybots. Therefore I want to
      do the following steps:
      1) In this CL for V8: create a new directory for the clusterfuzz corpus
      2) In chromium: use the new corpus directory
      3) In v8: clean up the old directory to use it on the trybots.
      
      R=bradnelson@chromium.org
      CC=mmoroz@chromium.org
      
      Change-Id: If690022558bb5780edf5a3649fb9745ef9c7407a
      Reviewed-on: https://chromium-review.googlesource.com/490367
      Commit-Queue: Brad Nelson <bradnelson@chromium.org>
      Reviewed-by: 's avatarBrad Nelson <bradnelson@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#44991}
      1f629aac
  11. 27 Apr, 2017 1 commit