https://codereview.chromium.org/1274453002/diff/1/src/heap/spaces.cc
File src/heap/spaces.cc (right):
https://codereview.chromium.org/1274453002/diff/1/src/heap/spaces.cc#newcode1410
src/heap/spaces.cc:1410:
heap()->incremental_marking()->Step(bytes_allocated,
Calling step is is a no-op in this case. ResetAllocationInfo is always
called within the GC. if (heap_->gc_state() != Heap::NOT_IN_GC ... will
bail out immediately.
https://codereview.chromium.org/1274453002/diff/1/src/heap/spaces.cc#newcode1517
src/heap/spaces.cc:1517: top_on_previous_step_ = new_top;
On 2015/08/04 19:37:11, ofrobots wrote:
I think it might be good to refactor this into a new
NewSpace::InlineAllocationStep method. I can do that. I wanted to keep
the
initial CL minimal.
Yes, good idea.
https://codereview.chromium.org/1274453002/
--
--
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.
