1. 21 May, 2019 2 commits
  2. 20 May, 2019 1 commit
  3. 17 May, 2019 3 commits
  4. 16 May, 2019 2 commits
  5. 15 May, 2019 1 commit
  6. 10 May, 2019 1 commit
  7. 29 Apr, 2019 1 commit
  8. 24 Apr, 2019 1 commit
  9. 17 Apr, 2019 1 commit
  10. 05 Apr, 2019 1 commit
  11. 04 Apr, 2019 1 commit
    • Deepti Gandluri's avatar
      [wasm] Move is_growable from JSArrayBuffer object to AllocationData · b0077b3b
      Deepti Gandluri authored
      Some state related to WasmMemories is cached on the JSArrayBuffer
      object (is_growable, is_wasm_memory). The problem with this is in
      some PostMessage flows, this information can get lost depending on
      how JSArrayBuffers are deserialized. In this particular case when
      the WasmMemory is postMessaged, it goes through the Blink
      DedicatedWorkerMessagingProxy::PostMessageToWorkerGlobalScope flow,
      which reconstructs the ArrayBuffer from the backing store, and size,
      and loses the is_growable flag, leading to a failure to grow memory.
      
      Moving the is_growable flag so that AllocationData can be the source
      of truth for all wasm memory state, and is consistently preserved
      across PostMessage.
      
      Change-Id: I775f66ddeff68b8cafc18b75ca5460dfb0343c8b
      Bug: v8:9065
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549789
      Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
      Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
      Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#60641}
      b0077b3b
  12. 28 Mar, 2019 2 commits
  13. 27 Mar, 2019 1 commit
  14. 19 Mar, 2019 1 commit
  15. 14 Mar, 2019 1 commit
  16. 07 Mar, 2019 1 commit
  17. 06 Mar, 2019 1 commit
  18. 27 Feb, 2019 1 commit
  19. 25 Feb, 2019 1 commit
  20. 08 Feb, 2019 1 commit
  21. 04 Feb, 2019 1 commit
  22. 29 Jan, 2019 2 commits
  23. 08 Jan, 2019 1 commit
  24. 24 Dec, 2018 2 commits
  25. 21 Dec, 2018 1 commit
  26. 11 Dec, 2018 1 commit
  27. 05 Dec, 2018 1 commit
  28. 04 Dec, 2018 1 commit
  29. 29 Nov, 2018 1 commit
    • Aseem Garg's avatar
      Revert "[wasm] Add I64AtomicWait implementation" · f4775f1c
      Aseem Garg authored
      This reverts commit 9436e8a8.
      
      Reason for revert: Breaks TSAN.
      
      Original change's description:
      > [wasm] Add I64AtomicWait implementation
      > 
      > Bug=v8:8075
      > R=​adamk@chromium.org,binji@chromium.org
      > 
      > Change-Id: I11ef5daccd043123b23e60c93ee0df79cabe9ccd
      > Reviewed-on: https://chromium-review.googlesource.com/c/1342948
      > Reviewed-by: Adam Klein <adamk@chromium.org>
      > Reviewed-by: Ben Smith <binji@chromium.org>
      > Commit-Queue: Aseem Garg <aseemgarg@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#57917}
      
      TBR=binji@chromium.org,adamk@chromium.org,aseemgarg@chromium.org
      
      Change-Id: Ic82ce8794410a0d4d19de07abd9bb8a7aaff1c1c
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/1351303Reviewed-by: 's avatarAseem Garg <aseemgarg@chromium.org>
      Commit-Queue: Aseem Garg <aseemgarg@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#57919}
      f4775f1c
  30. 28 Nov, 2018 1 commit
  31. 26 Nov, 2018 1 commit
  32. 23 Nov, 2018 1 commit
  33. 21 Nov, 2018 1 commit