v8/test/mjsunit/wasm/print-code.js
Andreas Haas 4852286284 [wasm] Add --no-wasm-lazy-compilation for tests that need it
Some tests assume that liftoff code is available immediately after
compilation. Add the `--no-wasm-lazy-compilation` flag to these tests
so that they work even after shipping lazy compilation.

R=clemensb@chromium.org

Bug: v8:12926
Change-Id: I839610221390822b90b25e1bef3ae727fa33d1ca
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3804862
Reviewed-by: Clemens Backes <clemensb@chromium.org>
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/main@{#82162}
2022-08-03 11:05:45 +00:00

34 lines
1012 B
JavaScript

// Copyright 2018 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.
// Force TurboFan code for serialization.
// Flags: --allow-natives-syntax --print-wasm-code --no-liftoff
// Flags: --no-wasm-lazy-compilation
// Just test that printing the code of the following wasm modules does not
// crash.
d8.file.execute('test/mjsunit/wasm/wasm-module-builder.js');
(function print_deserialized_code() {
// https://crbug.com/849656
print(arguments.callee.name);
var builder = new WasmModuleBuilder();
builder.addImport('', 'imp', kSig_i_v);
builder.addFunction('main', kSig_i_v)
.addBody([
kExprCallFunction,
0,
])
.exportFunc();
var wire_bytes = builder.toBuffer();
var module = new WebAssembly.Module(wire_bytes);
print('serializing');
var buff = %SerializeWasmModule(module);
print('deserializing');
module = %DeserializeWasmModule(buff, wire_bytes);
})();