369f1ffb42
If a new jump table is created and lazy compilation is enabled, we need to initialize the new jump table with jumps to the lazy compile table. R=ahaas@chromium.org Bug: chromium:1016515 Change-Id: I5749470d4a08af903a6a4da13dbe5454ee6db309 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1873687 Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#64462}
21 lines
657 B
JavaScript
21 lines
657 B
JavaScript
// Copyright 2019 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: --wasm-lazy-compilation
|
|
|
|
load('test/mjsunit/wasm/wasm-module-builder.js');
|
|
|
|
var builder = new WasmModuleBuilder();
|
|
var func = builder.addFunction('func', kSig_i_v).addBody([kExprI32Const, 1]);
|
|
var body = [];
|
|
for (let i = 0; i < 200; ++i) {
|
|
body.push(kExprCallFunction, func.index);
|
|
}
|
|
for (let i = 1; i < 200; ++i) {
|
|
body.push(kExprI32Add);
|
|
}
|
|
builder.addFunction('test', kSig_i_v).addBody(body).exportFunc();
|
|
var instance = builder.instantiate();
|
|
instance.exports.test();
|