c6a16c10dd
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}
27 lines
670 B
JavaScript
27 lines
670 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 --opt --no-always-opt
|
|
// The deopt count is stored in the feedback vector which gets cleared when
|
|
// bytecode is flushed, which --gc-interval can cause in stress modes.
|
|
// Flags: --noflush-bytecode --nostress-flush-bytecode
|
|
|
|
function foo() {};
|
|
%PrepareFunctionForOptimization(foo);
|
|
foo();
|
|
foo();
|
|
%OptimizeFunctionOnNextCall(foo);
|
|
foo();
|
|
|
|
assertOptimized(foo);
|
|
|
|
// Unlink the function.
|
|
%DeoptimizeFunction(foo);
|
|
|
|
assertUnoptimized(foo);
|
|
|
|
foo();
|
|
|
|
assertUnoptimized(foo);
|