v8/test/mjsunit/regress/regress-unlink-closures-on-deopt.js
Mythri A b62a7166c7 Fix flaky failure in mjsunit/regress/regress-unlink-closures-on-deopt
This is short-term fix for flaky failures on GC fuzzer. The closures
g1 and g2 have the same SFI and pending optimzed table treats them as
a single entry. This cl, adds %PrepareFunctionForOptimize after one of
them is optimized.

Bug: v8:9556
Change-Id: I1fd72da1baa5de2f7650e080f9b6d04b69dd6a16
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1719188
Reviewed-by: Georg Neis <neis@chromium.org>
Commit-Queue: Mythri Alle <mythria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#62934}
2019-07-26 12:00:11 +00:00

40 lines
853 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 --noalways-opt
function foo() {
function g(o) {
return o.f;
}
return g;
}
let g1 = foo();
let g2 = foo();
%PrepareFunctionForOptimization(g1);
g1({ f : 1});
g1({ f : 2});
g2({ f : 2});
g2({ f : 2});
%OptimizeFunctionOnNextCall(g1);
g1({ f : 1});
%PrepareFunctionForOptimization(g2);
%OptimizeFunctionOnNextCall(g2);
g2({ f : 2});
g1({});
assertUnoptimized(g1);
// Deoptimization of g1 should also deoptimize g2 because they should share
// the optimized code object. (Unfortunately, this test bakes in various
// other assumptions about dealing with optimized code, and thus might break
// in future.)
assertUnoptimized(g2);
g2({});