1. 24 Mar, 2018 4 commits
  2. 23 Mar, 2018 32 commits
  3. 22 Mar, 2018 4 commits
    • Junliang Yan's avatar
      PPC/s390: Reland^2: Remove SFI code field · a29de090
      Junliang Yan authored
      Port 51ded9d3
      
      Original Commit Message:
      
          This is a reland of d8f564ea
      
          Original change's description:
          > Reland: Remove SFI code field
          >
          > Remove the SharedFunctionInfo code field, inferring the code object
          > from the function_data field instead. In some cases, the function_data
          > field can now hold a Code object (e.g. some WASM cases).
          >
          > (Reland of https://chromium-review.googlesource.com/952452)
          >
          > TBR=mstarzinger@chromium.org
          >
          > Bug: chromium:783853
          > Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
          > Change-Id: I10ea5be7ceed1b51362a2fad9be7397624d69343
          > Reviewed-on: https://chromium-review.googlesource.com/970649
          > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
          > Reviewed-by: Yang Guo <yangguo@chromium.org>
          > Reviewed-by: Jakob Gruber <jgruber@chromium.org>
          > Reviewed-by: Leszek Swirski <leszeks@chromium.org>
          > Cr-Commit-Position: refs/heads/master@{#52136}
      
      R=leszeks@chromium.org, joransiu@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      LOG=N
      
      Change-Id: I86c5a46a866830a2150ff9366be12a09f111240f
      Reviewed-on: https://chromium-review.googlesource.com/976624Reviewed-by: 's avatarJoran Siu <joransiu@ca.ibm.com>
      Commit-Queue: Junliang Yan <jyan@ca.ibm.com>
      Cr-Commit-Position: refs/heads/master@{#52165}
      a29de090
    • Junliang Yan's avatar
      s390: [heap] Pass isolate to the OOM handler and add an OOM test. · e46772ea
      Junliang Yan authored
      Port 28190980
      
      Original Commit Message:
      
          This patch also moves Shell::Exit to base::OS::ExitProcess.
      
      R=ulan@chromium.org, joransiu@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      LOG=N
      
      Change-Id: I0a7dc051ed5a21ad9641d1d05182ea4240bc666a
      Reviewed-on: https://chromium-review.googlesource.com/976332Reviewed-by: 's avatarJoran Siu <joransiu@ca.ibm.com>
      Commit-Queue: Junliang Yan <jyan@ca.ibm.com>
      Cr-Commit-Position: refs/heads/master@{#52164}
      e46772ea
    • Eric Holk's avatar
      [wasm] always allocate memory when guard regions are needed · d31dff84
      Eric Holk authored
      When using trap handlers, memory references do not get any checks inserted. This
      means there is no check for a null memory as happens when the memory size is
      0. Normally this would be correctly caught as an out of bounds access, since the
      low memory addresses are not normally mapped. However, if they were mapped for
      some reason, we would not catch the out of bounds access.
      
      The fix is to ensure WebAssembly instances always have a guard region even if
      the memory is size 0.
      
      This is a rewrite of 5e76ff5a
      
      Note that this can lead to a large amount of unnecessary address space usage,
      so we share a single reservation for empty array buffers.
      
      Bug: chromium:769637
      
      Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng
      Change-Id: Ia8e84be6d595e347d3d342959f2c374db1a3f683
      Reviewed-on: https://chromium-review.googlesource.com/702657Reviewed-by: 's avatarDeepti Gandluri <gdeepti@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Commit-Queue: Eric Holk <eholk@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52163}
      d31dff84
    • Clemens Hammacher's avatar
      [Liftoff] Fix conditional spilling · 2589ea08
      Clemens Hammacher authored
      On float comparisons, we need a scratch byte register for the setcc
      instruction, and if none is available, we spill. But this spilling code
      is skipped if one of the operands is NaN. The cache state is updated
      however, so following code assumes that the spill happened.
      This CL fixes this by spilling before checking for NaN, such that the
      spilling code is always executed.
      
      R=titzer@chromium.org
      
      Bug: v8:7582, v8:6600
      Change-Id: I768d8de14e494d3ebea181c1f9f3129a4b005396
      Reviewed-on: https://chromium-review.googlesource.com/973961Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52162}
      2589ea08