1. 20 May, 2016 1 commit
    • mlippautz's avatar
      [heap] Harden heap-related cctests · fdd9f6b9
      mlippautz authored
      - Move usable functions into proper heap-utils.h/.cc files and remove
        utils-inl.h file
      - Fix assumptions accross the board relying on certain behavior that is not
        invariant
      
      This is a requirement for modifying page size.
      
      BUG=chromium:581412
      LOG=N
      R=ulan@chromium.org
      
      Review-Url: https://codereview.chromium.org/1999753002
      Cr-Commit-Position: refs/heads/master@{#36410}
      fdd9f6b9
  2. 11 May, 2016 1 commit
  3. 14 Apr, 2016 1 commit
  4. 12 Apr, 2016 1 commit
  5. 11 Apr, 2016 2 commits
  6. 08 Apr, 2016 2 commits
    • jfb's avatar
      Revert of Fix printf formats (patchset #8 id:140001 of... · 4c4fdc2d
      jfb authored
      Revert of Fix printf formats (patchset #8 id:140001 of https://codereview.chromium.org/1869433004/ )
      
      Reason for revert:
      One small issue easily fixed here: https://codereview.chromium.org/1867333003/
      
      But it looks like MSVS 2013 doesn't like some of the formats and exists with the unhelpful:
      Stderr:
      f:\dd\vctools\crt\crtw32\stdio\output.c(1125) : Assertion failed: ("Incorrect
      format specifier", 0)
      
      It's easier to revert for now, I'll dig more into the docs:
      https://msdn.microsoft.com/en-us/library/56e442dc(v=vs.120).aspx
      https://msdn.microsoft.com/en-us/library/tcxf1dw6(v=vs.120).aspx
      
      And then resubmit, making sure I run these bots.
      
      Original issue's description:
      > Fix printf formats
      >
      > The usage of __attribute__((format(x, y)) was either wrong or missing from multiple functions, leading to erroneous formats. This CL:
      >
      >  - Imports PRINTF_FORMAT macro from Chrome's src/base/compiler-specific.h.
      >  - Uses it appropriately.
      >  - Imports Chrome's base/format_macros.h mainly to fix size_t formats (further cleanup could be done).
      >  - Fixes a bunch of incorrect formats.
      >
      > R= jochen@chromium.org, bmeurer@chromium.org, yangguo@chromium.org, ahaas@chromium.org
      >
      > Committed: https://crrev.com/6ebf9fbb93d31f9be41156a3325d58704ed4933d
      > Cr-Commit-Position: refs/heads/master@{#35365}
      
      TBR=jochen@chromium.org,bmeurer@chromium.org,yangguo@chromium.org,ahaas@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/1867383002
      
      Cr-Commit-Position: refs/heads/master@{#35366}
      4c4fdc2d
    • jfb's avatar
      Fix printf formats · 6ebf9fbb
      jfb authored
      The usage of __attribute__((format(x, y)) was either wrong or missing from multiple functions, leading to erroneous formats. This CL:
      
       - Imports PRINTF_FORMAT macro from Chrome's src/base/compiler-specific.h.
       - Uses it appropriately.
       - Imports Chrome's base/format_macros.h mainly to fix size_t formats (further cleanup could be done).
       - Fixes a bunch of incorrect formats.
      
      R= jochen@chromium.org, bmeurer@chromium.org, yangguo@chromium.org, ahaas@chromium.org
      
      Review URL: https://codereview.chromium.org/1869433004
      
      Cr-Commit-Position: refs/heads/master@{#35365}
      6ebf9fbb
  7. 06 Apr, 2016 1 commit
  8. 04 Apr, 2016 1 commit
  9. 29 Mar, 2016 4 commits
  10. 23 Mar, 2016 4 commits
  11. 22 Mar, 2016 1 commit
  12. 17 Mar, 2016 1 commit
  13. 11 Dec, 2015 1 commit
  14. 09 Dec, 2015 2 commits
  15. 08 Dec, 2015 1 commit
    • ulan's avatar
      Optimize clearing of map transitions. · 8c376b46
      ulan authored
      Instead of iterating the whole map space to find dead transitions,
      look in weak cell list and transition array list.
      
      Simple transitions are in the weak cell list.
      
      Full transitions are in the transitions array list.
      
      BUG=chromium:554488
      LOG=NO
      
      Review URL: https://codereview.chromium.org/1488593003
      
      Cr-Commit-Position: refs/heads/master@{#32684}
      8c376b46
  16. 04 Dec, 2015 1 commit
  17. 03 Dec, 2015 2 commits
  18. 24 Nov, 2015 1 commit
  19. 13 Nov, 2015 1 commit
  20. 12 Nov, 2015 2 commits
  21. 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
  22. 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
  23. 03 Nov, 2015 1 commit
  24. 28 Oct, 2015 1 commit
  25. 23 Oct, 2015 2 commits