1. 08 May, 2020 1 commit
  2. 29 Apr, 2020 1 commit
  3. 07 Feb, 2020 1 commit
  4. 03 Jul, 2018 1 commit
  5. 10 Oct, 2017 1 commit
    • Michael Lippautz's avatar
      [heap] Introduce on-hold concurrent marking work list · b7e6eb92
      Michael Lippautz authored
      When hitting objects that are allocated in the most recent lienar
      allocation area, the concurrent marker currently has to bail out to the
      main thread.
      
      However, we only have to delay processing those objects until we are at
      a safepoint, e.g. IM::Step(). With this change we flush those
      on-hold-objects back to the shared queue upon performing an incremental
      marking step.
      
      Bug: chromium:694255
      Change-Id: I25647d0fc581a5c4de0346bc394dc51062f65f70
      Reviewed-on: https://chromium-review.googlesource.com/707315
      Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
      Reviewed-by: 's avatarUlan Degenbaev <ulan@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#48424}
      b7e6eb92
  6. 05 Jul, 2017 1 commit
  7. 04 Jul, 2017 1 commit
  8. 27 Jun, 2017 1 commit
  9. 26 Jun, 2017 2 commits
  10. 23 Jun, 2017 1 commit