1. 31 Oct, 2018 3 commits
  2. 26 Oct, 2018 1 commit
  3. 24 Oct, 2018 2 commits
  4. 23 Oct, 2018 2 commits
  5. 01 Oct, 2018 1 commit
    • Michael Lippautz's avatar
      [heap] Fix ThinString scavenge · 0503f195
      Michael Lippautz authored
      Instead of writing the forwarding pointer of this object and treating it like
      an object that would survive on scavenge just write the actual string pointer
      to the outer slot. As a consequence, the ThingString will not look like a live
      object and is handled properly when pruning the external string table.
      
      Bug: v8:8249
      Test: test/cctest/heap/test-external-string-tracker.cc
      Change-Id: I975900213e2e4b598f298c8f78b6c6047c9e6da4
      Reviewed-on: https://chromium-review.googlesource.com/1252885Reviewed-by: 's avatarHannes Payer <hpayer@chromium.org>
      Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#56311}
      0503f195
  6. 26 Sep, 2018 1 commit
  7. 21 Sep, 2018 1 commit
  8. 17 Sep, 2018 1 commit
  9. 14 Sep, 2018 2 commits
    • Marja Hölttä's avatar
      Revert "[in-place weak refs] Fix MaybeObject function names" · 3a79fe23
      Marja Hölttä authored
      This reverts commit ad72d195.
      
      Reason for revert: Build failures on *san
      
      Original change's description:
      > [in-place weak refs] Fix MaybeObject function names
      > 
      > E.g., "ToWeakHeapObject" was misleading, since it didn't convert to a weak heap
      > object, instead returned a weakly pointed heap object. Change the function names
      > (in this case, to "GetHeapObjectIfWeak") to reflect this.
      > 
      > Also make casts explicit, if a MaybeObject is an Object, we can call cast<Object>().
      > 
      > BUG=v8:7308
      > 
      > Change-Id: I4ef078572b4f4415afe7e2e706d3bd684e16e47d
      > Reviewed-on: https://chromium-review.googlesource.com/1219025
      > Reviewed-by: Igor Sheludko <ishell@chromium.org>
      > Reviewed-by: Tobias Tebbi <tebbi@chromium.org>
      > Reviewed-by: Yang Guo <yangguo@chromium.org>
      > Reviewed-by: Andreas Haas <ahaas@chromium.org>
      > Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      > Commit-Queue: Marja Hölttä <marja@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#55906}
      
      TBR=ulan@chromium.org,marja@chromium.org,yangguo@chromium.org,ahaas@chromium.org,tebbi@chromium.org,ishell@chromium.org
      
      Change-Id: I054b578518e3f6fd7dbcddf0b56cc018726c1e7a
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:7308
      Reviewed-on: https://chromium-review.googlesource.com/1226874Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
      Commit-Queue: Marja Hölttä <marja@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55918}
      3a79fe23
    • Marja Hölttä's avatar
      [in-place weak refs] Fix MaybeObject function names · ad72d195
      Marja Hölttä authored
      E.g., "ToWeakHeapObject" was misleading, since it didn't convert to a weak heap
      object, instead returned a weakly pointed heap object. Change the function names
      (in this case, to "GetHeapObjectIfWeak") to reflect this.
      
      Also make casts explicit, if a MaybeObject is an Object, we can call cast<Object>().
      
      BUG=v8:7308
      
      Change-Id: I4ef078572b4f4415afe7e2e706d3bd684e16e47d
      Reviewed-on: https://chromium-review.googlesource.com/1219025Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
      Reviewed-by: 's avatarTobias Tebbi <tebbi@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Marja Hölttä <marja@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#55906}
      ad72d195
  10. 28 Aug, 2018 3 commits
  11. 24 Aug, 2018 2 commits
  12. 23 Aug, 2018 2 commits
  13. 30 Jul, 2018 1 commit
  14. 27 Jul, 2018 1 commit
  15. 10 Jul, 2018 1 commit
  16. 04 Jul, 2018 1 commit
  17. 19 Jun, 2018 1 commit
  18. 22 Mar, 2018 1 commit
  19. 05 Mar, 2018 3 commits
  20. 27 Feb, 2018 1 commit
  21. 21 Feb, 2018 1 commit
  22. 20 Dec, 2017 1 commit
  23. 14 Nov, 2017 1 commit
  24. 04 Sep, 2017 1 commit
  25. 25 Aug, 2017 1 commit
  26. 14 Aug, 2017 1 commit
    • Ulan Degenbaev's avatar
      [heap] Refactor object marking state (part 2). · 19ae2fc1
      Ulan Degenbaev authored
      This follows up 4af9cfcc by separating incremental marking state
      from the full MC marking state. Runtime and tests now use only
      the incremental marking state. The full MC marking state used
      by MC during atomic pause.
      
      This separation decouples atomicity of markbit accesses
      during incremental marking and during full MC.
      
      Bug: chromium:694255
      TBR: mlippautz@chromium.org
      Change-Id: Ia409ab06515cd0d1403a272a016633295c0d6692
      Reviewed-on: https://chromium-review.googlesource.com/612350
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47336}
      19ae2fc1
  27. 10 Aug, 2017 1 commit
    • Ulan Degenbaev's avatar
      [heap] Refactor object marking state. · 4af9cfcc
      Ulan Degenbaev authored
      This patch merges ObjectMarking and MarkingState. The new marking state
      encapsulates object marking, live byte tracking, and access atomicity.
      
      The old ObjectMarking calls are now replaced with calls to marking
      state. For example:
      ObjectMarking::WhiteToGrey<kAtomicity>(obj, marking_state(obj)
      becomes
      marking_state()->WhiteToGrey(obj)
      
      This simplifies custom handling of live bytes and allows to chose
      atomicity of markbit accesses depending on collector's state.
      
      This also decouples marking bitmap from the marking code, which will
      allows in future to use different data-structure for mark-bits.
      
      Bug: chromium:694255
      Change-Id: Ifb4bc0144187bac1c08f6bc74a9d5c618fe77740
      Reviewed-on: https://chromium-review.googlesource.com/602132
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47288}
      4af9cfcc
  28. 03 Aug, 2017 1 commit
  29. 02 Aug, 2017 1 commit
    • Ulan Degenbaev's avatar
      Revert "[heap] Add support for atomic access to page flags." · 74b1cbbd
      Ulan Degenbaev authored
      This reverts commit 35c923cc.
      
      Reason for revert: speculative revert for GC stress failure
      
      Original change's description:
      > [heap] Add support for atomic access to page flags.
      > 
      > This patch renames AsAtomicWord to AsAtomicPointer and
      > adds new AsAtomicWord that works with intptr_t.
      > 
      > Slot recording uses atomic page flag accessors.
      > 
      > BUG=chromium:694255
      > 
      > Change-Id: I1c692813244b41320182e9eea50462d1802fcd98
      > Reviewed-on: https://chromium-review.googlesource.com/597688
      > Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      > Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#47086}
      
      TBR=ulan@chromium.org,mlippautz@chromium.org
      
      Change-Id: Id77ce7970c54a55646c072787e88311f6f3e6e91
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: chromium:694255
      Reviewed-on: https://chromium-review.googlesource.com/598967Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#47094}
      74b1cbbd