v8/test/mjsunit/call-counts.js
mstarzinger 2aba89e336 Remove bogus flags from call-counts.js test.
The runtime flag in question makes no sense, because the feature cannot
be disabled without keeping the snapshot in sync. We should avoid having
the flag in our "mjsunit" test suite, so that CluserFuzz doesn't pick it
up. The test in question is already skipped, the change will not affect
test results on our waterfall.

R=mvstanton@chromium.org
TEST=mjsunit/call-counts
BUG=v8:4458
LOG=n

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

Cr-Commit-Position: refs/heads/master@{#31302}
2015-10-15 13:31:57 +00:00

47 lines
1.2 KiB
JavaScript

// Copyright 2015 the V8 project authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
// Flags: --allow-natives-syntax --noalways-opt
// We disable vector store ICs because slot indices change when this option
// is enabled.
// Locations in the type feedback vector where call counts are maintained for
// the two calls made from bar();
(function() {
const kFooCallExtraIndex = 5;
const kArrayCallExtraIndex = 7;
function GetCallCount(func, slot) {
var vector = %GetTypeFeedbackVector(func);
// Call counts are recorded doubled.
var value = %FixedArrayGet(vector, slot);
return Math.floor(value / 2);
}
function foo(a) { return a[3] * 16; }
function bar(a) {
var result = 0;
for (var i = 0; i < 10; i++) {
result = foo(a);
if (i % 2 === 0) {
var r = Array();
r[0] = 1;
result += r[0];
}
}
return result;
}
var a = [1, 2, 3];
bar(a);
assertEquals(10, GetCallCount(bar, kFooCallExtraIndex));
assertEquals(5, GetCallCount(bar, kArrayCallExtraIndex));
%OptimizeFunctionOnNextCall(bar);
bar(a);
})();