1. 04 May, 2022 6 commits
  2. 03 May, 2022 30 commits
  3. 02 May, 2022 4 commits
    • Frank Tang's avatar
      Reland "[Temporal] Fix Calendar.prototype.fields CSA" · 4776aee6
      Frank Tang authored
      This is a reland of commit 89600314
      
      Changes since revert: None, reverted wrong suspect CL
      
      Original change's description:
      > [Temporal] Fix Calendar.prototype.fields CSA
      >
      > Use LoadAndUntagToWord32ObjectField instead of LoadObjectField<Uint32T>
      > to load the flag since it is defined as
      >  flags: SmiTagged<JSTemporalCalendarFlags>;
      >
      > Otherwise LoadObjectField<Uint32T> will load the zero part when
      > v8_enable_pointer_compression = false
      >
      > Add unit tests to intl (because the problem only show up on calendar
      > other than non iso8601.
      >
      > Cq-Include-Trybots: luci.v8.try:v8_linux_mipsel_compile_rel,v8_linux_mips64el_compile_rel
      >
      >
      > Bug: v8:12848
      > Change-Id: I44b685af99dc9820dfa228447e2b42ae0a82464c
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3617388
      > Reviewed-by: Leszek Swirski <leszeks@chromium.org>
      > Commit-Queue: Frank Tang <ftang@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#80314}
      
      Bug: v8:12848
      Change-Id: I423ea5f0a4a30fc73546df208d24aec84db76eb4
      Cq-Include-Trybots: luci.v8.try:v8_linux_mipsel_compile_rel,v8_linux_mips64el_compile_rel
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3620838
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Commit-Queue: Shu-yu Guo <syg@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#80319}
      4776aee6
    • Shu-yu Guo's avatar
      Revert "cppgc: young-gen: Enable cppgc_enable_young_generation by default" · 61be01e9
      Shu-yu Guo authored
      This reverts commit 31009706.
      
      Reason for revert: UBSan failure: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20UBSan/21069/overview
      
      Original change's description:
      > cppgc: young-gen: Enable cppgc_enable_young_generation by default
      >
      > Oilpan Young Generation is now controlled by the runtime flag
      > --cppgc-young-generation.
      >
      > Bug: chromium:1029379
      > Change-Id: I9ded9637f43a2f86993cff898cd7f272a051ae3c
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3616728
      > Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
      > Commit-Queue: Anton Bikineev <bikineev@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#80312}
      
      Bug: chromium:1029379
      Change-Id: I18ac696380df5f77d0978072b8e5af2f2e305994
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3620839
      Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Auto-Submit: Shu-yu Guo <syg@chromium.org>
      Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
      Cr-Commit-Position: refs/heads/main@{#80318}
      61be01e9
    • Shu-yu Guo's avatar
      Revert "[Temporal] Fix Calendar.prototype.fields CSA" · f478546b
      Shu-yu Guo authored
      This reverts commit 89600314.
      
      Reason for revert: UBSAN errors in GC tests
      https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20UBSan/21069/overview
      
      Original change's description:
      > [Temporal] Fix Calendar.prototype.fields CSA
      >
      > Use LoadAndUntagToWord32ObjectField instead of LoadObjectField<Uint32T>
      > to load the flag since it is defined as
      >  flags: SmiTagged<JSTemporalCalendarFlags>;
      >
      > Otherwise LoadObjectField<Uint32T> will load the zero part when
      > v8_enable_pointer_compression = false
      >
      > Add unit tests to intl (because the problem only show up on calendar
      > other than non iso8601.
      >
      > Cq-Include-Trybots: luci.v8.try:v8_linux_mipsel_compile_rel,v8_linux_mips64el_compile_rel
      >
      >
      > Bug: v8:12848
      > Change-Id: I44b685af99dc9820dfa228447e2b42ae0a82464c
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3617388
      > Reviewed-by: Leszek Swirski <leszeks@chromium.org>
      > Commit-Queue: Frank Tang <ftang@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#80314}
      
      Bug: v8:12848
      Change-Id: I3a8af8acbbdfc5d0f5386f2a9d50d62b9f422fb8
      Cq-Include-Trybots: luci.v8.try:v8_linux_mipsel_compile_rel,v8_linux_mips64el_compile_rel
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3620837
      Auto-Submit: Shu-yu Guo <syg@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@{#80317}
      f478546b
    • Michael Lippautz's avatar
      Reland "[heap] Fix bogus object size computation" · 10eac4eb
      Michael Lippautz authored
      This is a reland of commit 445190bf
      
      The fix addresses the issue where object size accounting went out of
      sync because of right-trimmed LO in new space that were migrated with
      a different size than they were accounted for.
      
      The fix now iterates only live objects for size computation which
      avoids accessing reclaimed maps and fixes up the objects accounting.
      
      Original change's description:
      > [heap] Fix bogus object size computation
      >
      > The map of an object may be gone by the time we try to compute its
      > size for accounting purposes.
      >
      > Bug: chromium:1319217
      > Change-Id: I93cca766a8cedebf4ed30a3a65fd6eff5bc72bcf
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3605817
      > Reviewed-by: Dominik Inführ <dinfuehr@chromium.org>
      > Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
      > Cr-Commit-Position: refs/heads/main@{#80271}
      
      Bug: chromium:1319217
      Change-Id: I8d032edf96a4bf4b0faa4bbd9b0be247051c49fb
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3616507Reviewed-by: 's avatarDominik Inführ <dinfuehr@chromium.org>
      Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#80316}
      10eac4eb