Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(67)

Issue 6992025: WIP: Blocks for global handles.

Created:
9 years, 7 months ago by Vitaly Repeshko
Modified:
9 years, 7 months ago
CC:
v8-dev
Visibility:
Public.

Description

WIP: Blocks for global handles. R=vegorov@chromium.org

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+312 lines, -308 lines) Patch
M src/global-handles.h View 2 chunks +8 lines, -28 lines 0 comments Download
M src/global-handles.cc View 17 chunks +302 lines, -280 lines 2 comments Download
M src/utils.h View 1 chunk +2 lines, -0 lines 0 comments Download

Messages

Total messages: 1 (0 generated)
Vyacheslav Egorov (Chromium)
9 years, 7 months ago (2011-05-24 16:45:12 UTC) #1
I like it. Seems to be much cleaner then before (especially because there is no
free/deallocated duality).

I am a bit concerned about fragmentation which might negatively affect iteration
performance though.

http://codereview.chromium.org/6992025/diff/1/src/global-handles.cc
File src/global-handles.cc (right):

http://codereview.chromium.org/6992025/diff/1/src/global-handles.cc#newcode397
src/global-handles.cc:397: new NodeBlock(this);
Personally I don't like constructors with deep implicit side effects.

http://codereview.chromium.org/6992025/diff/1/src/global-handles.cc#newcode510
src/global-handles.cc:510: if (collector == SCAVENGER &&
!it.node()->is_independent()) continue;
Interesting: so skipping blocks with no young independent handles here does not
win us anything, does it?

Powered by Google App Engine
This is Rietveld 408576698