233cb0bfc6
The flag is on by default, so we don't need to specify it. More importantly, the tests are expected to work for any value of that flag. So don't force the flag but use whatever the test variant chooses. Note that in streaming-compile.js, the flag was accidentally specified as '-async-compilation'. I also removed that one. R=ahaas@chromium.org Change-Id: Ifad31160d266dda38cdd9dd1d73dad69bd2c2f2c Reviewed-on: https://chromium-review.googlesource.com/c/1325961 Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57406}
31 lines
969 B
JavaScript
31 lines
969 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: --expose-wasm --no-wait-for-wasm
|
|
|
|
load("test/mjsunit/wasm/wasm-constants.js");
|
|
load("test/mjsunit/wasm/wasm-module-builder.js");
|
|
|
|
(function CompileFunctionsTest() {
|
|
// Create a big module.
|
|
var builder = new WasmModuleBuilder();
|
|
|
|
builder.addMemory(1, 1, true);
|
|
for (i = 0; i < 100; i++) {
|
|
builder.addFunction("sub" + i, kSig_i_i)
|
|
.addBody([ // --
|
|
kExprGetLocal, 0, // --
|
|
kExprI32Const, i % 61, // --
|
|
kExprI32Sub]) // --
|
|
.exportFunc()
|
|
}
|
|
|
|
var buffer = builder.toBuffer();
|
|
// Start the compilation but do not wait for the promise to resolve
|
|
// with assertPromiseResult. This should not cause a crash.
|
|
WebAssembly.compile(buffer).then(
|
|
() => { print("success")},
|
|
() => { print("failed"); });
|
|
})();
|