1. 02 Sep, 2020 1 commit
  2. 25 Jun, 2020 2 commits
  3. 24 Jun, 2020 2 commits
  4. 16 Jun, 2020 2 commits
  5. 25 May, 2020 1 commit
  6. 06 May, 2020 1 commit
    • Jakob Gruber's avatar
      [snapshot] Clear reconstructable data prior to d8 stress_snapshot run · 3c422d1c
      Jakob Gruber authored
      The serializer currently cannot handle a heap state containing
      arbitrary compiled Code objects. As a quick fix for the
      --stress-snapshot d8 flag, we clear compiled data from the isolate
      prior to the serialize-deserialize-verify pass.
      
      With this change, mjsunit tests pass on x64.
      
      The %SerializeDeserializeNow() runtime function would require more
      work, since it is not possible to mutate the heap to this extent while
      still preserving a runnable host context and isolate. We will need
      another solution there.
      
      Drive-by: Skip the stress_snapshot variant except for the mjsunit
      suite.
      
      Tbr: machenbach@chromium.org
      Bug: v8:10493,v8:10416
      Change-Id: Ie110da8b51613fcd69c7f391d3cf8589d6b04dd8
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2182429Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#67585}
      3c422d1c
  7. 22 Apr, 2020 1 commit
  8. 27 Feb, 2020 1 commit
  9. 24 Feb, 2020 1 commit
  10. 18 Feb, 2020 1 commit
  11. 31 Oct, 2019 1 commit
  12. 22 Oct, 2019 1 commit
  13. 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
  14. 28 Aug, 2019 1 commit
    • Andreas Haas's avatar
      [wasm] Add proposal js-api spec tests to the testrunner · 4f34d353
      Andreas Haas authored
      At the moment we only run the js-api spec tests of the core API on our
      try bots. With the new staging process we want to introduce for
      WebAssembly language features, see
      https://docs.google.com/document/d/1hB8mpWmzmtaxZ8PuJEkAWLwFqXTjrw7mJ3Ge9W1dB4E,
      we also want to run the js-api spec tests of proposals for which we
      already staged the implementation. With this CL I do the following
      changes:
      
      1) The tools/wasm/update-wasm-spec-tests.sh now copies the js-api spec
         tests of the main spec and of the proposals to test/wasm-js/tests,
         and then uploads this directory to google cloud storage. The main
         spec tests are in test/wasm-js/tests, the proposal tests are in
         test/wasm-js/tests/proposals/PROPOSAL_NAME/.
      2) Adjust the test-runner in test/wasm-js to run tests in
         tests/* instead of data/test/js-api/*. Thereby it also runs the
         proposal tests in test/wasm-js/tests/proposals/PROPOSAL_NAME/.
         For the proposal tests, the test runner now also adds d8 flags.
      3) Remove the dependency to https://github.com/WebAssembly/spec from
         DEPS.
      4) Cleanup .gitignore and wasm-js.status
      5) Disable spec tests we don't pass with the new proposal.
      
      R=tmrts@chromium.org
      
      Bug: v8:9653
      Change-Id: Ib3420871f17cb146d6cc7868f5613942a7f79d84
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1768372
      Commit-Queue: Tamer Tas <tmrts@chromium.org>
      Reviewed-by: 's avatarTamer Tas <tmrts@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#63419}
      4f34d353
  15. 26 Feb, 2019 1 commit
  16. 04 Feb, 2019 1 commit
  17. 29 Jan, 2019 1 commit
  18. 24 Jan, 2019 1 commit
  19. 22 Jan, 2019 1 commit
  20. 19 Jan, 2019 1 commit
  21. 18 Jan, 2019 1 commit
    • Sven Sauleau's avatar
      [wasm] fix js-api table/grow · fc277117
      Sven Sauleau authored
      Fix WebAssembly's table/grow js-api. The argument is a unsigned long,
      this change refactors most of arithmetic and bounds checks type from
      int64 to uint32_t, according to the spec.
      
      Bug: v8:8319
      Cq-Include-Trybots: luci.chromium.try:linux-blink-rel
      Change-Id: Ia29121c930d7fb930668e54a5a769dae25234f2c
      Reviewed-on: https://chromium-review.googlesource.com/c/1351006
      Commit-Queue: Sven Sauleau <ssauleau@igalia.com>
      Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#58936}
      fc277117
  22. 16 Jan, 2019 1 commit
  23. 10 Jan, 2019 1 commit
  24. 07 Jan, 2019 1 commit
  25. 04 Jan, 2019 1 commit
  26. 10 Dec, 2018 1 commit
    • Sven Sauleau's avatar
      [wasm] fix js-api Memory and Table constructor · ff6544c5
      Sven Sauleau authored
      Fix and re-enable tests for WebAssembly's memory/constructor and
      table/constructor js-api.
      
      It introduces the '[EnforceRange] unsigned long' algorithm used
      to validate initial and maximum properties.
      
      The initial property is now required, by the switch to the Web IDL
      specification. Most of the input validations errors are now considered
      TypeError instead of RangeError.
      
      The WasmTableObject and WasmMemoryObject APIs use more consistently uint32_t
      to ensure integer range and remove the need for bounds checks.
      
      Cq-Include-Trybots: luci.chromium.try:linux-blink-rel
      Bug: v8:8319
      Change-Id: Iedd3ee6484ef688a5e96f93006eb6ca66d805a48
      Reviewed-on: https://chromium-review.googlesource.com/c/1354043
      Commit-Queue: Adam Klein <adamk@chromium.org>
      Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#58138}
      ff6544c5
  27. 07 Dec, 2018 1 commit
  28. 06 Dec, 2018 1 commit
  29. 05 Dec, 2018 1 commit
  30. 03 Dec, 2018 1 commit
  31. 18 Oct, 2018 1 commit
  32. 17 Oct, 2018 2 commits