1. 20 Aug, 2021 2 commits
  2. 16 Aug, 2021 3 commits
  3. 12 Aug, 2021 2 commits
  4. 11 Aug, 2021 2 commits
  5. 10 Aug, 2021 2 commits
    • Frank Tang's avatar
      [Temporal] Add some tests for Temporal.Calendar · dfa3dfa3
      Frank Tang authored
      All marked as FAIL at this stage.
      
      Bug: v8:11544
      Change-Id: I6e4346a57aa3df054d2ef5bd353544fba7fd855b
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3044350
      Commit-Queue: Frank Tang <ftang@chromium.org>
      Reviewed-by: 's avatarShu-yu Guo <syg@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#76211}
      dfa3dfa3
    • Georg Neis's avatar
      [compiler][test] Give tests control over finalization · 8b87e36e
      Georg Neis authored
      Some tests want to invalidate part of the VM state after an optimization
      has consumed the old state but before the code is installed.
      
      The existing mechanism for this is --block-concurrent-recompilation
      and %UnblockConcurrentRecompilation(). The former suspends optimization
      right after PrepareJob, before the background ExecuteJob phase. The
      intrinsic can then be used to unblock it again.
      
      This was good enough so far because the main "consume" work used to
      happen on the main thread. With concurrent inlining this is no longer
      true and we need something else.
      
      This CL introduces three intrinsics:
      
      %DisableOptimizationFinalization turns off automatic finalization of
      background optimizations.
      
      %FinalizeOptimization() can then be called at an appropriate time to
      manually finalize (and thus install) the code and reenable automatic
      finalization.
      
      In case one wants to perform some action on the main thread after the
      concurrent optimization has finished but before it is finalized, one can
      do so with the help of %WaitForBackgroundOptimization() (see tests).
      
      In a followup CL I'm removing the old mechanism since it now seems
      redundant.
      
      Bug: v8:12041, v8:7790
      Change-Id: Ib7195789105922eb7e4bff86dc5bc11e96a4f97b
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3071400
      Commit-Queue: Georg Neis <neis@chromium.org>
      Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#76190}
      8b87e36e
  6. 04 Aug, 2021 1 commit
  7. 03 Aug, 2021 1 commit
  8. 30 Jul, 2021 1 commit
  9. 29 Jul, 2021 1 commit
  10. 28 Jul, 2021 1 commit
  11. 27 Jul, 2021 3 commits
  12. 24 Jul, 2021 1 commit
    • Clemens Backes's avatar
      Reland "[liftoff][arm64] Zero-extend offsets also for SIMD" · 5e90a612
      Clemens Backes authored
      This is a reland of b99fe75c.
      The test is now skipped on non-SIMD hardware.
      
      Original change's description:
      > [liftoff][arm64] Zero-extend offsets also for SIMD
      >
      > This extends https://crrev.com/c/2917612 also for SIMD, which
      > (sometimes) uses the special {GetMemOpWithImmOffsetZero} method.
      > As part of this CL, that method is renamed to {GetEffectiveAddress}
      > which IMO is a better name. Also, it just returns a register to make the
      > semantic of that function obvious in the signature.
      >
      > Drive-by: When sign extending to 32 bit, only write to the W portion of
      >           the register. This is a bit cleaner, and I first thought that
      >           this would be the bug.
      >
      > R=jkummerow@chromium.org
      > CC=​thibaudm@chromium.org
      >
      > Bug: chromium:1231950, v8:12018
      > Change-Id: Ifaefe1f18e3a00534a30c99e3c37ed09d9508f6e
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3049073
      > Reviewed-by: Zhi An Ng <zhin@chromium.org>
      > Commit-Queue: Clemens Backes <clemensb@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#75898}
      
      TBR=zhin@chromium.org
      CC=jkummerow@chromium.org, thibaudm@chromium.org
      
      Bug: chromium:1231950, v8:12018
      Change-Id: I662b62fafe99389be7a6c23b970fdf3768f866cf
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3051610Reviewed-by: 's avatarClemens Backes <clemensb@chromium.org>
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#75901}
      5e90a612
  13. 23 Jul, 2021 5 commits
  14. 22 Jul, 2021 4 commits
  15. 21 Jul, 2021 2 commits
  16. 20 Jul, 2021 3 commits
  17. 19 Jul, 2021 4 commits
  18. 16 Jul, 2021 2 commits