1. 28 Jul, 2020 2 commits
  2. 27 Jul, 2020 1 commit
  3. 08 Jul, 2020 1 commit
  4. 24 Jun, 2020 1 commit
    • Clemens Backes's avatar
      [wasm] Make opcode properties constexpr · 852f43cd
      Clemens Backes authored
      This allows the compiler to eliminate more unneeded branches. Since all
      functions just do a lookup in a static table (either directly, or via
      compiling a switch to such a lookup), they are also good candidates for
      inlining, which is made possible by this change.
      
      One DCHECK is removed instead of pulling in the inl header, which would
      require more refactoring since the check is in a non-inl header.
      
      R=thibaudm@chromium.org
      TBR=jkummerow@chromium.org
      
      Bug: v8:10576
      Change-Id: If0fd25fd62c5f30b896fc67a5458a5ae475a6351
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2259944
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Reviewed-by: 's avatarThibaud Michaud <thibaudm@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#68508}
      852f43cd
  5. 23 Jun, 2020 1 commit
  6. 22 Jun, 2020 1 commit
  7. 18 Jun, 2020 3 commits
    • Ng Zhi An's avatar
      [wasm-simd][fuzzer] Add i8x16 i16x8 i32x4 bit_mask · 7c232b8f
      Ng Zhi An authored
      Bug: v8:10180
      Change-Id: Ic341e0de315b7d7b33dbad265c8fda9145a669da
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2243760Reviewed-by: 's avatarDeepti Gandluri <gdeepti@chromium.org>
      Commit-Queue: Zhi An Ng <zhin@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#68417}
      7c232b8f
    • Clemens Backes's avatar
      [wasm][fuzzer] Avoid creating temporary std::vectors · fe3531c4
      Clemens Backes authored
      Instead of creating temporary {std::vector}s (which always allocate on
      the heap) create more vectors on the stack, via initializer lists.
      
      As this is "only" a fuzzer, performance is not really critical, but
      still has some impact on the efficiency of the whole fuzzer.
      That said, this CL is mostly a cleanup to replace unwanted code pattern
      by better code.
      
      R=jkummerow@chromium.org
      
      Change-Id: I924c15e5d64ed584fc96c85715eef1dca5aef150
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2249928
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#68413}
      fe3531c4
    • Manos Koukoutos's avatar
      [wasm-gc] Change ValueType representation to account for new types · 52f65296
      Manos Koukoutos authored
      Motivation:
      Changes to the typed function references and gc proposals solidified
      the notion of heap type, clarified nullable vs. non-nullable reference
      types, and introduced rtts, which contain an integer depth field in
      addition to a heap type. This required us to overhaul our ValueType
      representation, which results in extensive changes.
      
      To keep this CL "small", we do not try to implement the binary encoding
      as described in the proposals, but rather devise a simpler one of our
      own (see below). Also, we do not try to implement additional
      functionality for the new types.
      
      Changes:
      - Introduce HeapType. Move heap types from ValueType to HeapType.
      - Introduce Nullability for reference types.
      - Rework ValueType helper methods.
      - Introduce rtts in ValueType with an integer depth field. Include depth
        in the ValueType encoding.
      - Make the constructor of ValueType private, instead expose static
        functions which explicitly state what they create.
      - Change every switch statement on ValueType::Kind. Sometimes, we need
        nested switches.
      - Introduce temporary constants in ValueTypeCode for nullable types,
        use them for decoding.
      - In WasmGlobalObject, split 'flags' into 'raw_type' and 'is_mutable'.
      - Change IsSubtypeOfRef to IsSubtypeOfHeap and implement changes in
        subtyping.
      - kWasmFuncRef initializers are now non-nullable. Initializers are
        only required to be subtypes of the declared global type.
      - Change tests and fuzzers as needed.
      
      Bug: v8:7748
      Change-Id: If41f783bd4128443b07e94188cea7dd53ab0bfa5
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2247657
      Commit-Queue: Manos Koukoutos <manoskouk@chromium.org>
      Reviewed-by: 's avatarClemens Backes <clemensb@chromium.org>
      Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#68408}
      52f65296
  8. 15 Jun, 2020 1 commit
  9. 09 Jun, 2020 1 commit
  10. 08 Jun, 2020 1 commit
  11. 03 Jun, 2020 2 commits
  12. 29 May, 2020 1 commit
  13. 27 May, 2020 2 commits
  14. 21 May, 2020 1 commit
  15. 20 May, 2020 3 commits
  16. 19 May, 2020 1 commit
  17. 18 May, 2020 3 commits
  18. 15 May, 2020 2 commits
  19. 14 May, 2020 2 commits
  20. 12 May, 2020 1 commit
  21. 08 May, 2020 1 commit
  22. 06 May, 2020 1 commit
  23. 05 May, 2020 1 commit
  24. 30 Apr, 2020 1 commit
  25. 29 Apr, 2020 1 commit
  26. 28 Apr, 2020 1 commit
  27. 27 Apr, 2020 1 commit
  28. 09 Apr, 2020 1 commit
  29. 18 Mar, 2020 1 commit