Commit a2676962 authored by ulan's avatar ulan Committed by Commit bot

Reland "[heap] Fix a formatting bug in --trace-incremental-marking. (patchset...

Reland "[heap] Fix a formatting bug in --trace-incremental-marking. (patchset #2 id:20001 of https://codereview.chromium.org/2324623004/ )"

This reverts commit 6c2a217e.

The performance regression in crbug.com/645411 was not caused
by the original CL.

TBR=mlippautz@chromium.org

Review-Url: https://codereview.chromium.org/2329983002
Cr-Commit-Position: refs/heads/master@{#39353}
parent 21cb1105
......@@ -810,7 +810,9 @@ void Heap::ScheduleIdleScavengeIfNeeded(int bytes_allocated) {
void Heap::FinalizeIncrementalMarking(GarbageCollectionReason gc_reason) {
if (FLAG_trace_incremental_marking) {
isolate()->PrintWithTimestamp("[IncrementalMarking] (%s).\n", gc_reason);
isolate()->PrintWithTimestamp(
"[IncrementalMarking] (%s).\n",
Heap::GarbageCollectionReasonToString(gc_reason));
}
HistogramTimerScope incremental_marking_scope(
......
......@@ -1162,7 +1162,7 @@ class Isolate {
bool IsIsolateInBackground() { return is_isolate_in_background_; }
void PrintWithTimestamp(const char* format, ...);
PRINTF_FORMAT(2, 3) void PrintWithTimestamp(const char* format, ...);
protected:
explicit Isolate(bool enable_serializer);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment