Commit 77836fec authored by Jaroslav Sevcik's avatar Jaroslav Sevcik Committed by Commit Bot

[profiler] Do not log timer events when --prof is specified.

Now hopefully getting it right, but still leaving in the confusing
flag implications.

Bug: v8:6520,chromium:766162
Change-Id: Idc6dca012bf0c9777b4a75cf424410ce5914c885
Reviewed-on: https://chromium-review.googlesource.com/671022Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
Commit-Queue: Jaroslav Sevcik <jarin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#48082}
parent 807d0abe
...@@ -18691,7 +18691,7 @@ MaybeHandle<JSDate> JSDate::New(Handle<JSFunction> constructor, ...@@ -18691,7 +18691,7 @@ MaybeHandle<JSDate> JSDate::New(Handle<JSFunction> constructor,
// static // static
double JSDate::CurrentTimeValue(Isolate* isolate) { double JSDate::CurrentTimeValue(Isolate* isolate) {
if (FLAG_log_timer_events || FLAG_prof_cpp) LOG(isolate, CurrentTimeEvent()); if (FLAG_log_internal_timer_events) LOG(isolate, CurrentTimeEvent());
// According to ECMA-262, section 15.9.1, page 117, the precision of // According to ECMA-262, section 15.9.1, page 117, the precision of
// the number in a Date object representing a particular instant in // the number in a Date object representing a particular instant in
......
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