I added bottlenecks for object allocation events and object movement events
and
most likely fixed a bug (see comments below).
https://codereview.chromium.org/325553002/diff/60001/src/mark-compact.cc
File src/mark-compact.cc (right):
https://codereview.chromium.org/325553002/diff/60001/src/mark-compact.cc#newcode2875
src/mark-compact.cc:2875: heap()->OnMoveEvent(dst, src, size);
Before this change we were not firing
PROFILE(isolate, SharedFunctionInfoMoveEvent(source->address(),
target->address()));
for such migrations unlike the ScavengingVisitor::MigrateObject(), which
seems wrong. Now we will fire.
https://codereview.chromium.org/325553002/diff/60001/src/spaces-inl.h
File src/spaces-inl.h (right):
https://codereview.chromium.org/325553002/diff/60001/src/spaces-inl.h#newcode256
src/spaces-inl.h:256:
This change is no longer needed, however I think that new version is
better.
https://codereview.chromium.org/325553002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
