06697f7a82
stress_flush_bytecode controls stress flushing of both bytecode and baseline code. So rename the flag to better reflect its functionality Bug: v8:11947 Change-Id: Ie6c124a476c3a7c6eabd1d75de030ee15fe78e32 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3062567 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/master@{#76043}
27 lines
668 B
JavaScript
27 lines
668 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: --no-flush-bytecode --no-stress-flush-code
|
|
|
|
function foo() {};
|
|
%PrepareFunctionForOptimization(foo);
|
|
foo();
|
|
foo();
|
|
%OptimizeFunctionOnNextCall(foo);
|
|
foo();
|
|
|
|
assertOptimized(foo);
|
|
|
|
// Unlink the function.
|
|
%DeoptimizeFunction(foo);
|
|
|
|
assertUnoptimized(foo);
|
|
|
|
foo();
|
|
|
|
assertUnoptimized(foo);
|