Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(358)

Issue 16758007: Make sure CallIC is in monomorphic state when starting profiling in NativeAccessorNameInProfile2 (Closed)

Created:
7 years, 6 months ago by yurys
Modified:
7 years, 6 months ago
Reviewers:
loislo, alph, Jakob Kummerow
CC:
v8-dev
Visibility:
Public.

Description

Make sure CallIC is in monomorphic state when starting profiling in NativeAccessorNameInProfile2 Changed cctest/test-cpu-profiler/NativeAccessorNameInProfile2 to make a few warm-up cycles before starting profiler so that accessor invocations performed via monomorphic inline caches and slow paths traces do not distort the profile. Drive-by: removed logging code that was used to diagnose NativeAccessorNameInProfile2 failures on Windows. BUG=None R=jkummerow@chromium.org, loislo@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=15055

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+19 lines, -20 lines) Patch
M test/cctest/test-cpu-profiler.cc View 7 chunks +19 lines, -20 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
yurys
7 years, 6 months ago (2013-06-11 07:22:03 UTC) #1
loislo
lgtm
7 years, 6 months ago (2013-06-11 07:28:57 UTC) #2
Jakob Kummerow
lgtm
7 years, 6 months ago (2013-06-11 07:58:22 UTC) #3
yurys
7 years, 6 months ago (2013-06-11 08:32:56 UTC) #4
Message was sent while issue was closed.
Committed patchset #1 manually as r15055 (presubmit successful).

Powered by Google App Engine
This is Rietveld 408576698