0798cc5867
Due to the previous change to that function, we can end up with set (non-null) fields even when the overall serialized_ field is unset. This can cause DCHECK failures (I don't think it's otherwise observable). Bug: chromium:1142240,v8:7790 Change-Id: I2711fae8a73438277caf7aa539f24d628b03153c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2497170 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#70753}
21 lines
413 B
JavaScript
21 lines
413 B
JavaScript
// Copyright 2020 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
|
|
|
|
function foo() {}
|
|
for (let i = 0; i < 100000; ++i) {
|
|
foo = foo.bind();
|
|
}
|
|
|
|
function main() {
|
|
foo();
|
|
foo();
|
|
}
|
|
|
|
%PrepareFunctionForOptimization(main);
|
|
main();
|
|
%OptimizeFunctionOnNextCall(main);
|
|
main();
|