1. 17 Jan, 2018 1 commit
  2. 14 Dec, 2017 1 commit
    • Ulan Degenbaev's avatar
      [heap] Emit trace event for background GC tasks. · 2031503a
      Ulan Degenbaev authored
      The following events in v8.gc category are emitted:
      - V8.GC_BACKGROUND_ARRAY_BUFFER_FREE
      - V8.GC_BACKGROUND_STORE_BUFFER
      - V8.GC_BACKGROUND_UNMAPPER
      - V8.GC_MC_BACKGROUND_EVACUATE_COPY
      - V8.GC_MC_BACKGROUND_EVACUATE_UPDATE_POINTERS
      - V8.GC_MC_BACKGROUND_MARKING
      - V8.GC_MC_BACKGROUND_SWEEPING
      - V8.GC_MINOR_MC_BACKGROUND_EVACUATE_COPY
      - V8.GC_MINOR_MC_BACKGROUND_EVACUATE_UPDATE_POINTERS
      - V8.GC_MINOR_MC_BACKGROUND_MARKING
      - V8.GC_SCAVENGER_BACKGROUND_SCAVENGE_PARALLEL
      
      Bug: chromium:758183
      Change-Id: I04368f75ac740cbc832a864609709e5a46f5baef
      Reviewed-on: https://chromium-review.googlesource.com/825203
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarHannes Payer <hpayer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#50107}
      2031503a
  3. 08 Dec, 2017 1 commit
    • Ulan Degenbaev's avatar
      [heap] Use unchecked length getter for concurrent marking of FixedArray. · 12779b16
      Ulan Degenbaev authored
      If the fixed array is being concurrently left-trimmed then checked
      getter can assert because the length is not necessarily a Smi.
      
      This patch uses unchecked length getter to cache the length as Object*.
      Only if the marker manages to color the array black, we are guaranteed
      that the cached length is a Smi.
      
      This patch also uses unchecked cast for FixedArray in HeapVisitor
      for concurrent marker.
      
      Note that this patch only affects debug mode.
      
      Bug: chromium:694255
      Change-Id: I5016a2234a9f5fb98b498e06f5d1428b3f1cc3c6
      Reviewed-on: https://chromium-review.googlesource.com/817554
      Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
      Reviewed-by: 's avatarMichael Lippautz <mlippautz@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49970}
      12779b16
  4. 06 Dec, 2017 1 commit
  5. 04 Dec, 2017 1 commit
  6. 28 Nov, 2017 1 commit
  7. 26 Oct, 2017 2 commits
  8. 23 Oct, 2017 1 commit
  9. 17 Oct, 2017 1 commit
  10. 11 Oct, 2017 2 commits
  11. 10 Oct, 2017 2 commits
  12. 09 Oct, 2017 3 commits
  13. 06 Oct, 2017 2 commits
  14. 25 Sep, 2017 1 commit
  15. 15 Sep, 2017 1 commit
  16. 29 Aug, 2017 1 commit
  17. 28 Aug, 2017 1 commit
  18. 22 Aug, 2017 1 commit
  19. 21 Aug, 2017 2 commits
  20. 14 Aug, 2017 1 commit
  21. 11 Aug, 2017 4 commits
  22. 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
  23. 07 Aug, 2017 3 commits
  24. 03 Aug, 2017 1 commit
  25. 02 Aug, 2017 2 commits
  26. 01 Aug, 2017 1 commit
  27. 28 Jul, 2017 1 commit