Skip to content

V
V8
Switch branch/tag
  1. 11 Dec, 2015 1 commit
  3. 09 Dec, 2015 2 commits
  5. 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
  7. 04 Dec, 2015 1 commit
  9. 03 Dec, 2015 2 commits
  11. 24 Nov, 2015 1 commit
  13. 12 Nov, 2015 1 commit
  15. 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
  17. 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
  19. 03 Nov, 2015 1 commit
  21. 28 Oct, 2015 1 commit
  23. 23 Oct, 2015 2 commits
  25. 16 Oct, 2015 2 commits
  27. 30 Sep, 2015 1 commit
  29. 21 Sep, 2015 1 commit
  31. 21 Aug, 2015 1 commit
  33. 19 Aug, 2015 1 commit
  35. 17 Aug, 2015 1 commit
  37. 06 Aug, 2015 1 commit
  39. 31 Jul, 2015 1 commit
  41. 21 Jul, 2015 1 commit
  43. 17 Jun, 2015 1 commit
  45. 15 Jun, 2015 1 commit
  47. 09 Jun, 2015 1 commit
  49. 29 May, 2015 1 commit
  51. 26 May, 2015 2 commits
  53. 22 May, 2015 1 commit
  55. 21 May, 2015 1 commit
  57. 18 Feb, 2015 1 commit
  59. 09 Feb, 2015 1 commit
  61. 23 Jan, 2015 1 commit
  63. 22 Dec, 2014 1 commit