v8/test/mjsunit/regress/regress-crbug-757199.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

32 lines
494 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
var obj1 = {};
var obj2 = {};
function h() {}
h.prototype = obj2;
function g(v) {
v.constructor;
}
function f() {
g(obj1);
};
%PrepareFunctionForOptimization(f);
obj1.x = 0;
f();
obj1.__defineGetter__('x', function() {});
g(obj2);
obj2.y = 0;
%OptimizeFunctionOnNextCall(f);
f();