1. 30 Mar, 2022 2 commits
  2. 25 Mar, 2022 4 commits
  3. 24 Mar, 2022 1 commit
  4. 23 Mar, 2022 2 commits
  5. 19 Mar, 2022 1 commit
  6. 18 Mar, 2022 1 commit
    • Marja Hölttä's avatar
      Revert "[rab/gsab] Temporarily stage --harmony-rab-gsab to enable fuzzing" · 95b8cb9c
      Marja Hölttä authored
      This reverts commit f198f35d.
      
      Reason for revert: Got enough fuzzer bugs to work on
      
      Original change's description:
      > [rab/gsab] Temporarily stage --harmony-rab-gsab to enable fuzzing
      >
      > Please revert this CL if it causes any trouble!
      >
      > Bug: v8:11111
      > Change-Id: I6061fdc0aed82952f093ede9ecd252be1ac99519
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3528495
      > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
      > Commit-Queue: Marja Hölttä <marja@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#79499}
      
      Bug: v8:11111
      Change-Id: I9eef57eeba72116cc97c347abe2b56277855b797
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3535779
      Commit-Queue: Marja Hölttä <marja@chromium.org>
      Auto-Submit: Marja Hölttä <marja@chromium.org>
      Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/main@{#79524}
      95b8cb9c
  7. 16 Mar, 2022 2 commits
  8. 15 Mar, 2022 1 commit
  9. 14 Mar, 2022 1 commit
  10. 09 Mar, 2022 1 commit
  11. 08 Mar, 2022 1 commit
  12. 03 Mar, 2022 3 commits
  13. 02 Mar, 2022 1 commit
    • Jakob Gruber's avatar
      [maglev] Basic tiering to Maglev · 123c38a5
      Jakob Gruber authored
      When --maglev is set, tier up to Maglev from unoptimized tiers based on
      --interrupt-budget-for-maglev, initially set to 40KB (which should very
      roughly by 1/10th of the time until the TF tierup decision is made).
      On the first interrupt, a non-concurrent optimization to Maglev is
      requested, which the next call to the marked function will perform.
      
      - There is no support for tiering from Maglev to TF yet.
      - Maglev's language support is minimal and tests are not expected to
        pass with --maglev.
      - Disable --maglev by default for now.
      
      Drive-by: fixes related to Maglev flag definitions.
      
      Bug: v8:7700
      Change-Id: I121bb3f4f3830fdd20e1d4a12d3e04f08a99be38
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3500302Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#79328}
      123c38a5
  14. 24 Feb, 2022 4 commits
  15. 23 Feb, 2022 1 commit
  16. 21 Feb, 2022 2 commits
  17. 18 Feb, 2022 5 commits
    • Junliang Yan's avatar
      Reland "s390x: [baseline] enable sparkplug on s390x" · 1b0cef51
      Junliang Yan authored
      This is a reland of 78bc7852
      
      Original change's description:
      > s390x: [baseline] enable sparkplug on s390x
      >
      > Change-Id: I4646bb0f3f6291c97bb4b397d6248b9bdaa2059a
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3439641
      > Reviewed-by: Victor Gomes <victorgomes@chromium.org>
      > Commit-Queue: Junliang Yan <junyan@redhat.com>
      > Cr-Commit-Position: refs/heads/main@{#78959}
      
      Change-Id: I1f2ce6622d6a6b20c197e23beeee3ee5b0aa32f4
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3471523Reviewed-by: 's avatarVictor Gomes <victorgomes@chromium.org>
      Commit-Queue: Junliang Yan <junyan@redhat.com>
      Cr-Commit-Position: refs/heads/main@{#79176}
      1b0cef51
    • Michael Achenbach's avatar
      Revert "[shared-struct] Prototype JS shared structs" · c1078b5e
      Michael Achenbach authored
      This reverts commit 1025bf26.
      
      Reason for revert: https://crbug.com/v8/12645
      
      Original change's description:
      > [shared-struct] Prototype JS shared structs
      >
      > Unlike the Stage 1 proposal, for simplicity the prototype does not add
      > any new syntax, instead opting for exposing a SharedStructType
      > constructor which takes an array of field names. This type constructor
      > returns constructors for shared structs.
      >
      > Shared structs can be shared across Isolates, are fixed layout, have no
      > prototype, have no .constructor, and can only store primitives and
      > other shared structs.
      >
      > The initial prototype does not have TurboFan support.
      >
      > Bug: v8:12547
      > Change-Id: I23bdd819940b42139692bcdb53d372099b0d4426
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3390643
      > Reviewed-by: Tobias Tebbi <tebbi@chromium.org>
      > Reviewed-by: Marja Hölttä <marja@chromium.org>
      > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
      > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org>
      > Commit-Queue: Shu-yu Guo <syg@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#79156}
      
      Bug: v8:12547
      Change-Id: I44f2b8bb7487b4d39ba1282585e0b2282501230f
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3474676
      Auto-Submit: Michael Achenbach <machenbach@chromium.org>
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Owners-Override: Michael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#79170}
      c1078b5e
    • Samuel Groß's avatar
      Split V8_OS_MACOSX into V8_OS_DARWIN and V8_OS_MACOS · a1faaf06
      Samuel Groß authored
      Previously, V8_OS_MACOSX was, somewhat confusingly, also used for iOS.
      With this CL, V8_OS_DARWIN will be set on both macOS and iOS,
      V8_OS_MACOS only on macOS, and V8_OS_IOS only on iOS.
      
      This CL also renames V8_TARGET_OS_MACOSX to V8_TARGET_OS_MACOS and
      renames platform-xnu.cc to platform-darwin.cc.
      
      Change-Id: I4bcafc7c337586662114144f6c7ccf47d978da1f
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3468577Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
      Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Commit-Queue: Samuel Groß <saelo@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#79167}
      a1faaf06
    • Dominik Inführ's avatar
      [heap] Add flag for disabling map space · 2b63d5d0
      Dominik Inführ authored
      Now that we are able to compact map space, we can also get rid of the
      map space and allocate maps in the old space instead. This CL introduces
      a FLAG_map_space for enabling/disabling the map space but the map space
      remains enabled by default for now.
      
      Without a separate space for maps, the GC can't prevent relocation of
      maps anymore. Therefore this CL always allows compaction of maps when
      running without a map space. Rename flag to --compact-maps to better fit
      this scenario.
      
      mkgrokdump and debug_helper also need to be updated to look for maps
      also in the old space. The map space is now optional.
      
      Bug: v8:12578
      Change-Id: Ic4e4abd0b58bee26e64329b1c92dbccb07d8105a
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3424483Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Reviewed-by: 's avatarSeth Brenith <seth.brenith@microsoft.com>
      Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#79165}
      2b63d5d0
    • Dominik Inführ's avatar
      [compiler] Always use full version of RecordWrite builtin · 1b437aa8
      Dominik Inführ authored
      When we know that the value in a write barrier is a map, we know that
      we are not going to have an old-to-new reference (maps are always in
      old generation). Therefore we also don't really need the generational
      barrier in RecordWrite. While this is technically correct, we don't
      gain much from this optimization. The inline and out-of-line generated
      code for the barrier is still the same as in all other cases. Which
      means that outside marking we don't even reach the RecordWrite builtin.
      Most write barrier executions happen outside incremental marking, hence
      performance of the incremental marking barrier isn't critical. This CL
      always uses the full RecordWrite builtin using a flag in order to
      allow for an easy revert.
      
      This CL is motivated by the shared heap work, which needs an additional
      always-on barrier in the future (similar to OLD_TO_NEW) to keep a
      OLD_TO_SHARED remembered set up-to-date. While maps are always in the
      old generation, they maybe by located in the shared heap.
      
      Bug: v8:11708
      Change-Id: I71a6ded2547a0b2bbb9bbbd796dbcae0987b2232
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3471854Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#79160}
      1b437aa8
  18. 17 Feb, 2022 1 commit
  19. 15 Feb, 2022 5 commits
  20. 11 Feb, 2022 1 commit