1. 02 Jul, 2020 1 commit
  2. 25 Jun, 2020 1 commit
  3. 25 May, 2020 1 commit
  4. 22 Apr, 2020 1 commit
  5. 22 Oct, 2019 1 commit
  6. 05 Sep, 2019 1 commit
    • Andreas Haas's avatar
      Reland [wasm] Stage wasm-bigint · 69719dd4
      Andreas Haas authored
      There was no problem with the original CL. I just had a problem with
      my local git branches.
      
      Original message:
      
      The implementation on wasm-bigint has been done, as far as I can tell.
      There are no spec tests yet, only an out-dated copy of the original
      spec tests which don't pass anymore. Therefore I disabled all the tests
      for now and created a tracking bug at https://crbug.com/v8/9673.
      
      TBR=adamk@chromium.org
      
      Bug: v8:7741, v8:9673
      Change-Id: Ida7ccda4547cf3fdcdff151d8b02946b7aa534ca
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787420Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Commit-Queue: Andreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#63575}
      69719dd4
  7. 28 Aug, 2019 2 commits
  8. 17 Jul, 2019 1 commit
    • Andreas Haas's avatar
      [wasm][tests] Add proposal tests to the wasm spec tests · cd34523b
      Andreas Haas authored
      With this CL we add proposal tests to the wasm-spec-tests. For this I
      extended the update-wasm-spec-tests.sh script. Additionally to
      generating the spec tests it does the following:
      
      For each proposal it identifies those tests that are different to the
      spec tests, and then copies those tests also to the wasm-spec-tests
      directory.
      
      Additionally I adjusted the test runner of the wasm spec test to
      run the proposal tests with the correct flags.
      
      CC=binji@chromium.org
      R=clemensh@chromium.org
      
      Bug: v8:7581
      Change-Id: Idb7aa3c0a468ddb65b2ef3421def836561579cd9
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706470Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Commit-Queue: Andreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62777}
      cd34523b
  9. 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
  10. 18 Oct, 2018 1 commit
  11. 17 Oct, 2018 2 commits
  12. 25 Jan, 2018 1 commit
  13. 08 Dec, 2017 1 commit
  14. 10 Oct, 2017 1 commit
  15. 21 Jun, 2017 1 commit
  16. 09 Jun, 2017 1 commit
  17. 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
  18. 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
  19. 27 Apr, 2017 1 commit