1. 06 Sep, 2021 1 commit
  2. 03 Aug, 2021 1 commit
  3. 29 Jul, 2021 1 commit
  4. 14 Jun, 2021 1 commit
  5. 11 Jun, 2021 1 commit
  6. 01 Jun, 2021 1 commit
  7. 03 May, 2021 1 commit
  8. 22 Mar, 2021 1 commit
  9. 17 Mar, 2021 1 commit
  10. 09 Mar, 2021 1 commit
  11. 17 Feb, 2021 1 commit
  12. 16 Feb, 2021 1 commit
  13. 04 Feb, 2021 1 commit
  14. 29 Jan, 2021 1 commit
  15. 15 Jan, 2021 1 commit
  16. 08 Jan, 2021 1 commit
  17. 15 Dec, 2020 1 commit
  18. 03 Dec, 2020 1 commit
  19. 10 Sep, 2020 1 commit
  20. 27 Apr, 2020 1 commit
    • Clemens Backes's avatar
      [wasm][exn] Add test for manipulated prototype chain · 42bc23de
      Clemens Backes authored
      This adds a test which I suspected would fail, but luckily it doesn't.
      The idea is to catch a proper wasm exception in JS, then construct a new
      exception, but set the catched exception as the prototype. My suspicion
      was that we would still handle that new exception like a wasm exception,
      since the `WasmExceptionGetTag` and `WasmExceptionGetValues` runtime
      functions to a standard property lookup, which includes a prototype
      walk.
      Interestingly, the prototype walk is already skipped automatically when
      loading private symbols, so the implementation already supports this
      case correctly.
      Let's still add this test to have coverage for this case.
      
      R=jkummerow@chromium.org
      CC=aheejin@chromium.org
      
      Bug: v8:8091
      Change-Id: Idf9944cf47f96cca38e9678e9200bf03a39ea126
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2167438Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#67391}
      42bc23de
  21. 23 Mar, 2020 1 commit
  22. 08 Oct, 2019 1 commit
  23. 15 Jul, 2019 1 commit
  24. 30 Jan, 2019 1 commit
  25. 15 Jan, 2019 1 commit
  26. 10 Dec, 2018 1 commit
  27. 09 Oct, 2018 2 commits
    • Michael Starzinger's avatar
      [wasm] Add support for multiple catch blocks. · 2e007737
      Michael Starzinger authored
      This adds support for multiple catch blocks being attached to a single
      try block. The implemented semantics are that type checks are performed
      in order from top to bottom.
      
      Note that multiple catch blocks of the same type are not prohibited and
      will be accepted, making the second such block essentially unreachable.
      The current proposal neither explicitly allows nor prohibits it.
      
      R=clemensh@chromium.org
      TEST=mjsunit/wasm/exceptions
      BUG=v8:8091
      
      Change-Id: I31e7a07a7cffdd909a58342e00f05e52ed1a3182
      Reviewed-on: https://chromium-review.googlesource.com/c/1270591Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56478}
      2e007737
    • Michael Starzinger's avatar
      [wasm] Initial catch-all control flow wiring. · d56e29d1
      Michael Starzinger authored
      This adds support to wire control flow of catch-all expressions into an
      existing try-catch cascade. Note that multiple typed catch blocks are
      not yet supported, only one typed catch block followed by one catch-all
      block is supported.
      
      In case the explicit catch-all block is missing, we emulate the correct
      semantics by internally always emitting a catch-all containing a simple
      rethrow instruction.
      
      R=clemensh@chromium.org
      TEST=mjsunit/wasm/exceptions-catchall
      BUG=v8:8091
      
      Change-Id: I6b29a98c4f1a558fabe6012f4ba6c7b7d43529bb
      Reviewed-on: https://chromium-review.googlesource.com/c/1270585Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56476}
      d56e29d1
  28. 17 Sep, 2018 4 commits
  29. 04 Sep, 2018 3 commits
  30. 30 Aug, 2018 1 commit
    • Michael Starzinger's avatar
      [wasm] Add support for 'except_ref' value type. · f19a7068
      Michael Starzinger authored
      This adds experimental support for an 'except_ref' value type for caught
      exceptions as per the exception handling proposal. In the current for it
      is only allowed to have such types in the stack or in a local, support
      for having it as part of any signature was left out.
      
      The default value for a local of type 'except_ref' is the 'ref_null'
      value for now. Since this value cannot escape a wasm function, the
      concrete value is not actually observable.
      
      R=ahaas@chromium.org
      TEST=unittests/LocalDeclDecoderTest.ExceptRef,mjsunit/wasm/exceptions
      BUG=v8:8091
      
      Change-Id: I7bd65274327a833262f8749cbe0e24e737f6e0c1
      Reviewed-on: https://chromium-review.googlesource.com/1196510Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55526}
      f19a7068
  31. 29 Aug, 2018 1 commit
  32. 28 Aug, 2018 2 commits
  33. 25 Sep, 2017 1 commit
    • Karl Schimpf's avatar
      Add capability of throwing values in WASM · 49106e48
      Karl Schimpf authored
      This is a second attempt at landing CL 644866 which was reverted by
      CL 667019.
      
      Extends the current implementation of WASM exceptions to be able to
      throw exceptions with values (not just tags).
      
      A JS typed (uint_16) array is used to hold the thrown values. This
      allows all WASM types to be stored (i32, i64, f32, and f64) as well as
      be inspected in JS.
      
      The previous CL was reverted because the WASM compiler made calls to
      run time functions with tagged objects, which must not be done. To fix
      this, all run time calls use the thread-level isolate to hold the
      exception being processed.
      
      Bug: v8:6577
      Change-Id: I4b1ef7e2847b71a2fab8e9934a0531057db9de63
      Reviewed-on: https://chromium-review.googlesource.com/677056
      Commit-Queue: Karl Schimpf <kschimpf@chromium.org>
      Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarEric Holk <eholk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48148}
      49106e48