1. 06 Jun, 2016 1 commit
  2. 13 Apr, 2016 1 commit
  3. 23 Mar, 2016 1 commit
  4. 14 Mar, 2016 2 commits
  5. 25 Feb, 2016 1 commit
  6. 24 Feb, 2016 1 commit
    • ulan's avatar
      Revert of Replace slots buffer with remembered set. (patchset #14 id:250001 of... · 9146bc5e
      ulan authored
      Revert of Replace slots buffer with remembered set. (patchset #14 id:250001 of https://codereview.chromium.org/1703823002/ )
      
      Reason for revert:
      Revert because of canary crashes: crbug.com/589413
      
      Original issue's description:
      > Replace slots buffer with remembered set.
      >
      > Slots pointing to evacuation candidates are now recorded in the new RememberedSet<OLD_TO_OLD>.
      >
      > The remembered set is extended to support typed slots.
      >
      > During parallel evacuation all migration slots are recorded in local slots buffers.
      > After evacuation all local slots are added to the remembered set.
      >
      > BUG=chromium:578883
      > LOG=NO
      >
      > Committed: https://crrev.com/2285a99ef6f7d52f4f0c4d88a7db4224443ee152
      > Cr-Commit-Position: refs/heads/master@{#34212}
      
      TBR=jochen@chromium.org,hpayer@chromium.org,mlippautz@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=chromium:578883
      
      Review URL: https://codereview.chromium.org/1725073003
      
      Cr-Commit-Position: refs/heads/master@{#34238}
      9146bc5e
  7. 23 Feb, 2016 1 commit
    • ulan's avatar
      Replace slots buffer with remembered set. · 2285a99e
      ulan authored
      Slots pointing to evacuation candidates are now recorded in the new RememberedSet<OLD_TO_OLD>.
      
      The remembered set is extended to support typed slots.
      
      During parallel evacuation all migration slots are recorded in local slots buffers.
      After evacuation all local slots are added to the remembered set.
      
      BUG=chromium:578883
      LOG=NO
      
      Review URL: https://codereview.chromium.org/1703823002
      
      Cr-Commit-Position: refs/heads/master@{#34212}
      2285a99e
  8. 16 Feb, 2016 1 commit
  9. 21 Jan, 2016 1 commit
  10. 11 Jan, 2016 1 commit
  11. 09 Nov, 2015 1 commit
    • mstarzinger's avatar
      [heap] Separate out optimized code map processing. · 087513d6
      mstarzinger authored
      This separates the post-processing step for optimized code maps out of
      the CodeFlusher. It uses the complete SharedFunctionInfo::Iterator to
      visit all candidates instead of gathering candidates during marking.
      
      Gathering candidates during marking no longer makes sense, now that the
      majority of SharedFunctionInfo objects will hold such an optimized code
      map. Also it reduces complexity of the implementation. Also conflating
      this mechanism with "code flushing" was confusing.
      
      This reverts commit 7f1fb29f.
      
      R=ulan@chromium.org
      
      Review URL: https://codereview.chromium.org/1418453008
      
      Cr-Commit-Position: refs/heads/master@{#31876}
      087513d6
  12. 05 Nov, 2015 4 commits
    • mstarzinger's avatar
      Revert of [heap] Separate out optimized code map processing. (patchset #2... · 7f1fb29f
      mstarzinger authored
      Revert of [heap] Separate out optimized code map processing. (patchset #2 id:20001 of https://codereview.chromium.org/1421903012/ )
      
      Reason for revert:
      Causes GC-Stress failures.
      
      Original issue's description:
      > [heap] Separate out optimized code map processing.
      >
      > This separates the post-processing step for optimized code maps out of
      > the CodeFlusher. It uses the complete SharedFunctionInfo::Iterator to
      > visit all candidates instead of gathering candidates during marking.
      >
      > Gathering candidates during marking no longer makes sense, now that the
      > majority of SharedFunctionInfo objects will hold such an optimized code
      > map. Also it reduces complexity of the implementation. Also conflating
      > this mechanism with "code flushing" was confusing.
      >
      > This reverts commit b6644e84.
      >
      > R=ulan@chromium.org
      >
      > Committed: https://crrev.com/bb7a5eb2d89bae25f2b5ecb9515669f0ac73c111
      > Cr-Commit-Position: refs/heads/master@{#31836}
      
      TBR=ulan@chromium.org
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/1412063012
      
      Cr-Commit-Position: refs/heads/master@{#31837}
      7f1fb29f
    • mstarzinger's avatar
      [heap] Separate out optimized code map processing. · bb7a5eb2
      mstarzinger authored
      This separates the post-processing step for optimized code maps out of
      the CodeFlusher. It uses the complete SharedFunctionInfo::Iterator to
      visit all candidates instead of gathering candidates during marking.
      
      Gathering candidates during marking no longer makes sense, now that the
      majority of SharedFunctionInfo objects will hold such an optimized code
      map. Also it reduces complexity of the implementation. Also conflating
      this mechanism with "code flushing" was confusing.
      
      This reverts commit b6644e84.
      
      R=ulan@chromium.org
      
      Review URL: https://codereview.chromium.org/1421903012
      
      Cr-Commit-Position: refs/heads/master@{#31836}
      bb7a5eb2
    • hablich's avatar
      Revert of [heap] Separate out optimized code map processing. (patchset #3... · b6644e84
      hablich authored
      Revert of [heap] Separate out optimized code map processing. (patchset #3 id:40001 of https://codereview.chromium.org/1426953006/ )
      
      Reason for revert:
      Breaks build: https://uberchromegw.corp.google.com/i/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/3565
      
      Original issue's description:
      > [heap] Separate out optimized code map processing.
      >
      > This separates the post-processing step for optimized code maps out of
      > the CodeFlusher. It uses the complete SharedFunctionInfo::Iterator to
      > visit all candidates instead of gathering candidates during marking.
      >
      > Gathering candidates during marking no longer makes sense, now that the
      > majority of SharedFunctionInfo objects will hold such an optimized code
      > map. Also it reduces complexity of the implementation. Also conflating
      > this mechanism with "code flushing" was confusing.
      >
      > R=ulan@chromium.org
      >
      > Committed: https://crrev.com/8ad6168d197dd167235c9d342ec7ce37b0daa88b
      > Cr-Commit-Position: refs/heads/master@{#31830}
      
      TBR=ulan@chromium.org,yangguo@chromium.org,mvstanton@chromium.org,mstarzinger@chromium.org
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/1434503003
      
      Cr-Commit-Position: refs/heads/master@{#31832}
      b6644e84
    • mstarzinger's avatar
      [heap] Separate out optimized code map processing. · 8ad6168d
      mstarzinger authored
      This separates the post-processing step for optimized code maps out of
      the CodeFlusher. It uses the complete SharedFunctionInfo::Iterator to
      visit all candidates instead of gathering candidates during marking.
      
      Gathering candidates during marking no longer makes sense, now that the
      majority of SharedFunctionInfo objects will hold such an optimized code
      map. Also it reduces complexity of the implementation. Also conflating
      this mechanism with "code flushing" was confusing.
      
      R=ulan@chromium.org
      
      Review URL: https://codereview.chromium.org/1426953006
      
      Cr-Commit-Position: refs/heads/master@{#31830}
      8ad6168d
  13. 17 Sep, 2015 1 commit
  14. 15 Sep, 2015 1 commit
  15. 21 Aug, 2015 1 commit
  16. 17 Aug, 2015 3 commits
  17. 14 Aug, 2015 1 commit
  18. 10 Aug, 2015 1 commit
    • mstarzinger's avatar
      [heap] Avoid overzealous inclusion of heap internal headers. · 65c8ecc6
      mstarzinger authored
      This is a first step towards constraining down the heap interface to
      just the heap.h file. Note that many includes still leak through that
      file to the global "src" directory, but there now is a single place
      controlling which declarations leak that way. Especially inclusion of
      inline header files within "heap" has been limited drastically.
      
      R=hpayer@chromium.org,mlippautz@chromium.org
      
      Review URL: https://codereview.chromium.org/1281233003
      
      Cr-Commit-Position: refs/heads/master@{#30092}
      65c8ecc6
  19. 04 Aug, 2015 2 commits
  20. 23 Apr, 2015 1 commit
  21. 16 Apr, 2015 1 commit
  22. 15 Apr, 2015 2 commits
  23. 09 Apr, 2015 1 commit
  24. 07 Apr, 2015 1 commit
  25. 19 Mar, 2015 1 commit
  26. 18 Mar, 2015 1 commit
  27. 27 Aug, 2014 1 commit
  28. 21 Aug, 2014 1 commit
  29. 05 Aug, 2014 1 commit
  30. 04 Aug, 2014 1 commit
  31. 03 Jun, 2014 1 commit
  32. 29 Apr, 2014 1 commit