v8/test/mjsunit/regress/regress-crbug-774459.js
Mathias Bynens c6a16c10dd [test] Add %PrepareForOptimization to even more tests
With bytecode flushing and lazy feedback allocation, we need to call
%PrepareForOptimization before we call %OptimizeFunctionOnNextCall,
ideally after declaring the function.

Bug: v8:8801, v8:8394, v8:9183
Change-Id: I3fb257282a30f6526a376a3afdedb44786320d34
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1648255
Commit-Queue: Mathias Bynens <mathias@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Mythri Alle <mythria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#62119}
2019-06-12 14:40:14 +00:00

21 lines
491 B
JavaScript

// Copyright 2017 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
(function() {
const m = new Map();
const k = Math.pow(2, 31) - 1;
m.set(k, 1);
function foo(m, k) {
return m.get(k | 0);
};
%PrepareFunctionForOptimization(foo);
assertEquals(1, foo(m, k));
assertEquals(1, foo(m, k));
%OptimizeFunctionOnNextCall(foo);
assertEquals(1, foo(m, k));
})();