Make sure CallIC is in monomorphic state when starting profiling in NativeAccessorNam...
authoryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 11 Jun 2013 08:32:48 +0000 (08:32 +0000)
committeryurys@chromium.org <yurys@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 11 Jun 2013 08:32:48 +0000 (08:32 +0000)
commitb90bd6987b78d5e0ff41c8d423d981e8b0ebf4d5
treeab34333967361d4aa89d8a0c1c508dd1aa3f1dba
parentc90e697a3003436ef2cf1e4e1965e50528006ba0
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

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@15055 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
test/cctest/test-cpu-profiler.cc