1. 24 Apr, 2019 1 commit
  2. 09 Apr, 2019 1 commit
  3. 08 Apr, 2019 1 commit
    • Michael Starzinger's avatar
      [wasm] Support reference types on interpreter entry. · 0bed5887
      Michael Starzinger authored
      This adds preliminary support for references types as argument or return
      values to functions that are redirected to the interpreter. The current
      interpreter entry stub remains unchanged, using one buffer area that is
      hidden from the GC. The corresponding {Runtime_WasmRunInterpreter} now
      correctly boxes/un-boxes reference types into handles. This switch to a
      handlified representation happens before any method that potentially
      triggers a GC is called.
      
      R=clemensh@chromium.org
      TEST=mjsunit/wasm/exceptions-anyref-interpreter
      BUG=v8:8091,v8:7581
      
      Change-Id: I41c766ed5ac877042d5964e72f3fd7df390c4e98
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557147
      Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#60684}
      0bed5887
  4. 25 Mar, 2019 1 commit
  5. 19 Mar, 2019 1 commit
  6. 18 Mar, 2019 1 commit
  7. 23 Jan, 2019 1 commit
    • Andreas Haas's avatar
      [wasm][anyref] Implement sub-typing of anyref, anyfunc, and nullref · 5d587693
      Andreas Haas authored
      For the reference types anyref, anyfunc, and nullref, there exist
      sub-typing rules. The spec says
      
      A reference type reftype1 matches a reference type reftype2 if and only
      if:
      
      * Either both reftype1 and reftype2 are the same.
      * Or reftype1 is nullref.
      * Or reftype2 is anyref.
      
      This CL introduces the type nullref for ref-null, and implements the
      sub-typing rules in the function-body-decoder.
      
      Note that because of the sub-typing check validation performance may
      regresses. In that case we can optimize the sub-typing check.
      
      R=titzer@chromium.org, clemensh@chromium.org
      
      Bug: v8:7581
      Change-Id: I55bab72a109f3374da3770d141b0fc8067aad8b2
      Reviewed-on: https://chromium-review.googlesource.com/c/1430061
      Commit-Queue: Andreas Haas <ahaas@chromium.org>
      Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#59043}
      5d587693
  8. 17 Jan, 2019 1 commit
  9. 15 Jan, 2019 1 commit
  10. 12 Oct, 2018 1 commit
  11. 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
  12. 12 Jul, 2018 1 commit
  13. 09 Jul, 2018 1 commit
  14. 07 May, 2018 1 commit
  15. 24 Apr, 2018 1 commit