1. 24 Oct, 2018 37 commits
  2. 23 Oct, 2018 3 commits
    • Jakob Kummerow's avatar
      Revert "[builtins] Fix Array.p.join length overflow and invalid string length handling" · 7a975d11
      Jakob Kummerow authored
      This reverts commit ec969ea3.
      
      Reason for revert: test fails consistently on arm bots.
      I can't repro the failure locally, but it does consume ~512MB of memory (for a single string, I think?), so my guess is that the bots don't have enough contiguous address space.
      
      Original change's description:
      > [builtins] Fix Array.p.join length overflow and invalid string length handling
      > 
      > - Fixes and simplify allocating the temporary fixed array for ToString-ed elements.
      >   - When the array size is greater than representable by an intptr, it overflowed into a negative value causing a non-negative assert to fail.
      >   - Simplify fallback behavior by always allocating a conservatively sized temporary fixed array. Previously, if the array had dictionary elements, the temporary fixed array was sized based on %GetNumberDictionaryNumberOfElements() and then resized when entering the fallback.
      > 
      > - Fixes related invalid string length handling. When the running total of the resulting string length overflowed or exceeded String::kMaxLength, a RangeError is thrown. Previously, this thrown RangeError bypassed JoinStackPop and left the receiver on the stack.
      > 
      > Bug: chromium:897404
      > Change-Id: I157b71ef04ab06125a5b1c3454e5ed3713bdb591
      > Reviewed-on: https://chromium-review.googlesource.com/c/1293070
      > Commit-Queue: Peter Wong <peter.wm.wong@gmail.com>
      > Reviewed-by: Jakob Gruber <jgruber@chromium.org>
      > Reviewed-by: Tobias Tebbi <tebbi@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#56907}
      
      TBR=danno@chromium.org,peter.wm.wong@gmail.com,jgruber@chromium.org,tebbi@chromium.org
      
      Change-Id: I8ca80bd75833aacc94ccb25ceb82bbc8880991db
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: chromium:897404
      Reviewed-on: https://chromium-review.googlesource.com/c/1297471Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
      Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56915}
      7a975d11
    • Yang Guo's avatar
      Revert "[heap] Clean-up MemoryChunk allocation area constants." · 0d75b76c
      Yang Guo authored
      This reverts commit 1d837093.
      
      Reason for revert: Speculative revert for https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Arm%20-%20debug/8158
      
      Original change's description:
      > [heap] Clean-up MemoryChunk allocation area constants.
      > 
      > Change-Id: I8ba59546ab93c7af98bc5ece2f0160628844dd92
      > Reviewed-on: https://chromium-review.googlesource.com/c/1280584
      > Reviewed-by: Yang Guo <yangguo@chromium.org>
      > Commit-Queue: Hannes Payer <hpayer@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#56908}
      
      TBR=ulan@chromium.org,yangguo@chromium.org,hpayer@chromium.org
      
      Change-Id: I0ce51513864d3f7e4337391dc510fb828c083d48
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/1296488Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56914}
      0d75b76c
    • Clemens Hammacher's avatar
      [wasm] Fix data race when deleting the CompilationState · d447883b
      Clemens Hammacher authored
      When resetting the {unique_ptr} to the {CompilationState} in the
      {NativeModule}, what actually happens is that first the pointer stored
      in the {unique_ptr} is reset to {nullptr}, then the destructor is
      called.
      The destructor of {CompilationState} cancels and waits for background
      compile jobs. While doing so, background compile jobs still try to
      access the {unique_ptr} in the {NativeModule}.
      
      This CL fixes this race by splitting the shutdown in two steps: First,
      cancel and wait the background compile jobs, and only later reset the
      pointer.
      
      R=ahaas@chromium.org
      
      Bug: v8:8359
      No-Tree-Checks: true
      Change-Id: Ifa3bdf3424dfd5a4712d33f8ca85f9382b1766a6
      Reviewed-on: https://chromium-review.googlesource.com/c/1296486
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56913}
      d447883b