[wasm] Add test for printing wasm code after deserialization

R=mstarzinger@chromium.org

Bug: chromium:849656
Change-Id: I4c1990e10905969c94913f434ec0013e5cbbfb19
Reviewed-on: https://chromium-review.googlesource.com/1087273
Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#53535}
This commit is contained in:
Clemens Hammacher 2018-06-05 18:17:47 +02:00 committed by Commit Bot
parent 423b8a2011
commit dd8356020f

View File

@ -0,0 +1,32 @@
// 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.
// Flags: --allow-natives-syntax --print-wasm-code
// Just test that printing the code of the following wasm modules does not
// crash.
load('test/mjsunit/wasm/wasm-constants.js');
load('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);
})();