Refactor incremental marking to use static visitor.

Refactor incremental marking to use static visitor.

This is a refactoring only change that switches incremental marking to
use a static object visitor. It also shares the common code between the
non-incremental and the incremental marker. Sharing that would require
semantical changes will be done later.

R=verwaest@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=12193

[Toon Verwaest, 2012-07-23 13:10:21]

Lgtm with comment.

https://chromiumcodereview.appspot.com/10816007/diff/1/src/incremental-markin...
File src/incremental-marking.cc (right):

https://chromiumcodereview.appspot.com/10816007/diff/1/src/incremental-markin...
src/incremental-marking.cc:882: JSFunction::kNonWeakFieldsEndOffset));
Is this the same as IncrementalMarkingMarkingVisitor::VisitJSFunction?

[Michael Starzinger, 2012-07-25 08:21:32]

Addressed comments.

https://chromiumcodereview.appspot.com/10816007/diff/1/src/incremental-markin...
File src/incremental-marking.cc (right):

https://chromiumcodereview.appspot.com/10816007/diff/1/src/incremental-markin...
src/incremental-marking.cc:882: JSFunction::kNonWeakFieldsEndOffset));
On 2012/07/23 13:10:21, Toon Verwaest wrote:
> Is this the same as IncrementalMarkingMarkingVisitor::VisitJSFunction?

Done. Yes, it's should be the same. Changed so that the static visitor is used
here as well.