v8: fix tracking of longest_step in IncrementalMarking.
authorernstm@chromium.org <ernstm@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 16 Jul 2014 13:19:31 +0000 (13:19 +0000)
committerernstm@chromium.org <ernstm@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 16 Jul 2014 13:19:31 +0000 (13:19 +0000)
longest_step is only output at the end of a mark-compact. We shouldn't
reset it after a Scavenge.

R=hpayer@chromium.org
BUG=

Review URL: https://codereview.chromium.org/395153003

git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22432 ce2b1a6d-e550-0410-aec6-3dcde31c8c00

src/incremental-marking.cc

index b80fb8e..da10d75 100644 (file)
@@ -662,7 +662,6 @@ void IncrementalMarking::UpdateMarkingDequeAfterScavenge() {
 
   steps_took_since_last_gc_ = 0;
   steps_count_since_last_gc_ = 0;
-  longest_step_ = 0.0;
 }