1. 16 Jun, 2015 1 commit
  2. 08 Jun, 2015 1 commit
  3. 01 Jun, 2015 1 commit
  4. 16 Apr, 2015 1 commit
  5. 10 Apr, 2015 1 commit
  6. 09 Apr, 2015 3 commits
  7. 07 Apr, 2015 1 commit
  8. 30 Mar, 2015 1 commit
  9. 28 Mar, 2015 1 commit
  10. 27 Mar, 2015 1 commit
    • ishell's avatar
      Revert of Reland "Filter invalid slots out from the SlotsBuffer after... · de018fbd
      ishell authored
      Revert of Reland "Filter invalid slots out from the SlotsBuffer after marking." (patchset #2 id:2 of https://codereview.chromium.org/1032833002/)
      
      Reason for revert:
      Reverting risky GC changes that block v8 roll.
      
      Original issue's description:
      > Reland "Filter invalid slots out from the SlotsBuffer after marking."
      >
      > > There are two reasons that could cause invalid slots appearance in SlotsBuffer:
      > > 1) If GC trims "tail" of an array for which it has already recorded a slots and then migrate another object to the "tail".
      > > 2) Tagged slot could become a double slot after migrating of an object to another map with "shifted" fields (for example as a result of generalizing immutable data property to a data field).
      >
      > > This CL also adds useful machinery that helps triggering incremental write barriers.
      >
      > > BUG=chromium:454297
      > > LOG=Y
      >
      > NOTRY=true
      >
      > Committed: https://crrev.com/f86aadd1d45c756467dff8e08a055b462d7a060b
      > Cr-Commit-Position: refs/heads/master@{#27433}
      
      TBR=machenbach@chromium.org,ulan@chromium.org
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/1041593002
      
      Cr-Commit-Position: refs/heads/master@{#27491}
      de018fbd
  11. 25 Mar, 2015 1 commit
    • ulan's avatar
      Reland "Filter invalid slots out from the SlotsBuffer after marking." · f86aadd1
      ulan authored
      > There are two reasons that could cause invalid slots appearance in SlotsBuffer:
      > 1) If GC trims "tail" of an array for which it has already recorded a slots and then migrate another object to the "tail".
      > 2) Tagged slot could become a double slot after migrating of an object to another map with "shifted" fields (for example as a result of generalizing immutable data property to a data field).
      
      > This CL also adds useful machinery that helps triggering incremental write barriers.
      
      > BUG=chromium:454297
      > LOG=Y
      
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/1032833002
      
      Cr-Commit-Position: refs/heads/master@{#27433}
      f86aadd1
  12. 24 Mar, 2015 4 commits
  13. 19 Mar, 2015 1 commit
  14. 18 Mar, 2015 1 commit
  15. 16 Mar, 2015 3 commits
  16. 11 Mar, 2015 1 commit
  17. 10 Mar, 2015 3 commits
  18. 09 Mar, 2015 2 commits
    • hpayer's avatar
      Eliminate invalid pointers in store buffer after marking. · aee169ec
      hpayer authored
      The store buffer can contain stale store buffer entries, i.e., slot in dead objects pointing to new space objects. These slots are treaded as live slots which cause problems with non-pointer fields and makes concurrent sweeping complicated. Removing these pointers from the store buffer before it is used makes life easier.
      
      BUG=
      
      Review URL: https://codereview.chromium.org/985453003
      
      Cr-Commit-Position: refs/heads/master@{#27068}
      aee169ec
    • ishell@chromium.org's avatar
      Revert of Remove slots that point to unboxed doubles from the... · 67a02321
      ishell@chromium.org authored
      Revert of Remove slots that point to unboxed doubles from the StoreBuffer/SlotsBuffer. (patchset #4 id:230001 of https://codereview.chromium.org/957273002/)
      
      Reason for revert:
      It caused a lot of Canary crashes.
      
      Original issue's description:
      > Remove slots that point to unboxed doubles from the StoreBuffer/SlotsBuffer.
      >
      > The problem is that tagged slot could become a double slot after migrating of an object to another map with "shifted" fields (for example as a result of generalizing immutable data property to a data field).
      > This CL also adds useful machinery that helps triggering incremental write barriers.
      >
      > BUG=chromium:454297
      > LOG=Y
      >
      > Committed: https://crrev.com/9633ebabd405c264d33f603f8798c31f59418dcd
      > Cr-Commit-Position: refs/heads/master@{#27054}
      
      TBR=verwaest@chromium.org,hpayer@chromium.org
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=chromium:454297
      
      Review URL: https://codereview.chromium.org/991793002
      
      Cr-Commit-Position: refs/heads/master@{#27063}
      67a02321
  19. 06 Mar, 2015 1 commit
  20. 25 Feb, 2015 1 commit
  21. 05 Feb, 2015 1 commit
  22. 08 Jan, 2015 1 commit
  23. 15 Dec, 2014 1 commit
  24. 10 Dec, 2014 1 commit
  25. 24 Nov, 2014 1 commit
  26. 22 Nov, 2014 2 commits
  27. 11 Nov, 2014 1 commit
  28. 10 Nov, 2014 2 commits