Reviewers: Hannes Payer, Michael Starzinger,

Message:
PTAL

Description:
Make GCTracer persistent.

This is essentially https://codereview.chromium.org/390823003/. It turns
out that it's safe to use a persistent GCTracer instead
of creating and destroying GCTracers for each GC, because
Scavenge and Mark-Sweep steps never overlap, and the tracking of
incremental marking also happens separately for the two types of GC.
Tracking of incremental marking will be moved into the GCTracer in a
follow-up patch.

[email protected],[email protected]
BUG=

Please review this at https://codereview.chromium.org/403543002/

SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge

Affected files (+189, -176 lines):
  M src/heap.h
  M src/heap.cc
  M src/mark-compact.h
  M src/mark-compact.cc


--
--
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.

Reply via email to