4a5b7e32c4
It originates from the era where we used to run a separate preparse step before parsing and store the function data. Now the usage of preparser is something completely different, so this flag doesn't make sense any more. In addition, this way we get more test coverage for preparser (for small scripts). BUG= Review-Url: https://codereview.chromium.org/2513563002 Cr-Commit-Position: refs/heads/master@{#41110}
25 lines
477 B
JavaScript
25 lines
477 B
JavaScript
// Copyright 2016 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
|
|
|
|
let x;
|
|
function f(a) {
|
|
x += a;
|
|
}
|
|
function g(a) {
|
|
f(a); return x;
|
|
}
|
|
function h(a) {
|
|
x = a; return x;
|
|
}
|
|
|
|
function boom() { return g(1) }
|
|
|
|
assertEquals(1, h(1));
|
|
assertEquals(2, boom());
|
|
assertEquals(3, boom());
|
|
%OptimizeFunctionOnNextCall(boom);
|
|
assertEquals(4, boom());
|