1. 03 Aug, 2017 35 commits
  2. 02 Aug, 2017 5 commits
    • Deepti Gandluri's avatar
      [wasm] Implement atomic add/sub operations. · ac774a36
      Deepti Gandluri authored
       - Decode logic for atomic operations
       - Implementations for I32AtomicAdd, I32AtomicAdd8U, I32AtomicAdd16U,
      I32AtomicSub, I32AtomicSub8U, I32AtomicSub16U
       - cctest value helpers for Uint16/Uint8 types
      
      R=binji@chromium.org, bbudge@chromium.org, bradnelson@chromium.org
      
      BUG=v8:6532
      
      Change-Id: I710ee8ef566c5e33866afdf5b47375c2ea6fdbe6
      Reviewed-on: https://chromium-review.googlesource.com/595241Reviewed-by: 's avatarBill Budge <bbudge@chromium.org>
      Reviewed-by: 's avatarBrad Nelson <bradnelson@chromium.org>
      Reviewed-by: 's avatarBen Smith <binji@chromium.org>
      Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47102}
      ac774a36
    • Ulan Degenbaev's avatar
      Disable mjsunit/wasm/js-api on GC stress bots. · 5a506a9a
      Ulan Degenbaev authored
      Bug: chromium:751825
      No-Tree-Checks: true
      Change-Id: I8e9e5c030dca001a8dc881d8fdeefa5c140f3792
      Reviewed-on: https://chromium-review.googlesource.com/599047Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47101}
      5a506a9a
    • Karl Schimpf's avatar
      Reland "Start migration of try/throw/catch to match proposal." · ad49b7b4
      Karl Schimpf authored
      This is a reland of 470a1001
      Original change's description:
      > Start migration of try/throw/catch to match proposal.
      > 
      > This CL does the first baby steps on moving the current (experimental)
      > exception handling to match that of the WebAssembly proposal.
      > 
      > It does the following:
      > 
      > 1) Use exception tags instead of integers.
      > 
      > 2) Only handle empty exception signatures (i.e. no values associated
      >    with the exception tag.
      > 
      > 3) Only handle one catch clause.
      > 
      > 4) Be sure to rethrow the exception if the exception tag does not match.
      > 
      > Note: There are many things that need to be fixed, and are too
      > numerous to list here. However, the code should have TODO's on each
      > missing parts of the implementation.
      > 
      > Also note that the code currently doesn't handle nested catch blocks,
      > nor does it change the throw value being an integer. Rather, the
      > integer value is still being thrown, and currently is the exception
      > tag. Therefore, we don't build an exception object. This is the reason
      > why this CL doesn't handle exceptions that pass values.
      > 
      > Also, the current implementation still can't handle multiple modules
      > because tag resolution (between) modules has not be implemented yet.
      > 
      > Bug: v8:6577
      > Change-Id: Id6d08b641b3c42d1eec7d4db582f2dab35406114
      > Reviewed-on: https://chromium-review.googlesource.com/591910
      > Reviewed-by: Brad Nelson <bradnelson@chromium.org>
      > Commit-Queue: Karl Schimpf <kschimpf@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#47087}
      
      Bug: v8:6577
      Change-Id: I41c3309827c292cb787681a95aaef7cf9b931835
      Reviewed-on: https://chromium-review.googlesource.com/598968Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Reviewed-by: 's avatarBrad Nelson <bradnelson@chromium.org>
      Commit-Queue: Brad Nelson <bradnelson@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47100}
      ad49b7b4
    • Jeremy Roman's avatar
      Expose v8::TypedArray::kMaxLength. · 19fee8b2
      Jeremy Roman authored
      There is an API check failure if values larger than i::Smi::kMaxValue are
      provided, but it is inconvenient for API users to know what this value is
      (and SIZE_MAX and INT_MAX are both incorrect).
      
      This is analogous to v8::String::kMaxLength.
      
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Bug: chromium:750788
      Change-Id: Ic3e0da62aeacfeb996122595232aa0ea8744517e
      Reviewed-on: https://chromium-review.googlesource.com/594677Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Jeremy Roman <jbroman@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47099}
      19fee8b2
    • Adam Klein's avatar
      Enable --harmony-strict-legacy-accessor-builtins by default · 74edfccd
      Adam Klein authored
      This behavior has been staged successfully without a bug report, and
      has been shipped in the latest versions of Firefox and Safari.
      
      Bug: v8:5070
      Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel
      Change-Id: I084cae2cc303d6a213bd6789297b91656e162d6b
      Reviewed-on: https://chromium-review.googlesource.com/595129Reviewed-by: 's avatarDaniel Ehrenberg <littledan@chromium.org>
      Commit-Queue: Adam Klein <adamk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47098}
      74edfccd