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}
24 lines
735 B
JavaScript
24 lines
735 B
JavaScript
// Copyright 2018 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 --trace-turbo --trace-turbo-graph
|
|
// Flags: --trace-turbo-cfg-file=test/mjsunit/tools/turbo.cfg
|
|
// Flags: --trace-turbo-path=test/mjsunit/tools
|
|
|
|
// Only trace the "add" function:
|
|
// Flags: --trace-turbo-filter=add
|
|
|
|
// The idea behind this test is to make sure we do not crash when using the
|
|
// --trace-turbo flag given different sort of inputs.
|
|
|
|
(function testOptimizedJS() {
|
|
function add(a, b) {
|
|
return a + b;
|
|
};
|
|
%PrepareFunctionForOptimization(add);
|
|
add(21, 21);
|
|
%OptimizeFunctionOnNextCall(add);
|
|
add(20, 22);
|
|
})();
|