1. 17 Feb, 2022 2 commits
  2. 16 Feb, 2022 2 commits
  3. 15 Feb, 2022 1 commit
  4. 11 Feb, 2022 2 commits
  5. 10 Feb, 2022 2 commits
  6. 09 Feb, 2022 1 commit
  7. 08 Feb, 2022 2 commits
  8. 07 Feb, 2022 1 commit
  9. 04 Feb, 2022 1 commit
  10. 03 Feb, 2022 4 commits
  11. 02 Feb, 2022 2 commits
  12. 01 Feb, 2022 2 commits
  13. 31 Jan, 2022 3 commits
  14. 28 Jan, 2022 1 commit
  15. 27 Jan, 2022 2 commits
    • Manos Koukoutos's avatar
      [wasm-gc] Implement iso-recursive types · fe531e1f
      Manos Koukoutos authored
      This CL replaces the equirecursive type system for wasm-gc with the
      isorecursive hybrid type system presented here:
      https://github.com/WebAssembly/gc/issues/257.
      
      In broad strokes, this includes the following changes:
      - In the module decoder, remove equirecursive types. Implement recursive
        type groups, subtype definitions, and function/struct/array
        definitions. Treat nominal modules as syntactic sugar of an
        isorecursive module, where all types belong in the same recursive
        group.
      - Remove rtt.sub and all related infrastructure.
      - Change subtyping to work with explicit supertypes only.
      - Add ValidSubtypeDefinition in subtyping, to check that subtype
        declarations are valid during decoding.
      - Remove the subtyping cache.
      - Add support for functions to have specific signature index in
        WasmModuleBuilder and in test-gc.cc.
      - Adapt tests.
      
      Current restrictions:
      - Recursive groups are not stored beyond decoding.
      - Type canonicalization is not implemented. No tests relying on types
        being considered identical post-canonicalization.
      - No cross-module subtyping is possible. Tests relying on cross-module
        subtyping have been commented out.
      
      Bug: v8:7748
      Change-Id: I69fd04ecc5611f6230c95d5c89d1c520163fffae
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3416239Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Manos Koukoutos <manoskouk@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#78816}
      fe531e1f
    • Samuel Groß's avatar
      [sandbox] Sandboxify WasmInstanceObject::memory_start · 09784fa1
      Samuel Groß authored
      This field points to the start of the WASM memory buffer for the
      instance, which is an ArrayBuffer and so guaranteed to be located inside
      the sandbox if it is enabled. As such, this simply turns the field into
      a sandboxed pointer field.
      
      Bug: chromium:1218005
      Change-Id: I847aebf5c29fcf1ab1163809350204db5b685a10
      Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng,v8_linux_arm64_sim_heap_sandbox_dbg_ng
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3359630Reviewed-by: 's avatarClemens Backes <clemensb@chromium.org>
      Commit-Queue: Samuel Groß <saelo@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#78805}
      09784fa1
  16. 26 Jan, 2022 3 commits
  17. 25 Jan, 2022 1 commit
  18. 24 Jan, 2022 4 commits
  19. 17 Jan, 2022 1 commit
  20. 14 Jan, 2022 1 commit
  21. 12 Jan, 2022 2 commits