1. 05 May, 2020 9 commits
  2. 04 May, 2020 26 commits
  3. 03 May, 2020 1 commit
  4. 02 May, 2020 1 commit
  5. 01 May, 2020 3 commits
    • Milad Farazmand's avatar
      PPC/s390: Add bit left-rotation machine operator · 14785e51
      Milad Farazmand authored
      Port c0eee179
      
      Original Commit Message:
      
          ROL will be optional operator as arm, arm64 only have ROR.
      
          The reason for this CL is inefficient Wasm codegen for 64-bit
          left-rotation.
      
      R=duongn@microsoft.com, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      LOG=N
      
      Change-Id: I2803237712e45235ac53be07a28b4dc0c0f4a329
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2173574Reviewed-by: 's avatarJunliang Yan <jyan@ca.ibm.com>
      Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com>
      Cr-Commit-Position: refs/heads/master@{#67521}
      14785e51
    • Deepti Gandluri's avatar
      [wasm-simd] Remove interpreter tier of SIMD tests · 3c400825
      Deepti Gandluri authored
      As per the all-hands a couple of weeks ago, the interpreter will
      be removed soon. Remove running tests on this tier, so we no longer
      put effort into maintaining tests for this tier.
      
      Change-Id: I9fce0f3a7cd869d6ccecf1c1f820b794e89858e1
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2175021Reviewed-by: 's avatarZhi An Ng <zhin@chromium.org>
      Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#67520}
      3c400825
    • Seth Brenith's avatar
      [debug] Don't crash when breaking on entry to functions with heap vars · 3c20dfed
      Seth Brenith authored
      Any function with heap-allocated variables starts by creating and
      pushing a new context for its execution. When entering the debugger due
      to the stack check in the beginning of InterpreterEntryTrampoline, the
      function has not yet had a chance to push that new context. The code in
      ScopeIterator currently assumes that any function which needs a context
      already has one by the time the debugger attempts to iterate scopes, but
      in this case that assumption is invalid, which can cause a null deref.
      
      This change introduces a new function ScopeIterator::NeedsAndHasContext
      to replace previous calls to current_scope_->NeedsContext(). This new
      function checks for the case where the current scope matches the closure
      scope but the context matches the containing context for the function,
      which implies that the function has not yet pushed its own context.
      
      Bug: v8:10319, chromium:1038747
      Change-Id: I29636f269c44d35b68d8446769d17170eed50e89
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2168021
      Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
      Reviewed-by: 's avatarSimon Zünd <szuend@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#67519}
      3c20dfed