[wasm] binary and test for hosts' integration tests

test/mjsunit/wasm/ensure-wasm-binaries-up-to-date.js

Index: test/mjsunit/wasm/ensure-wasm-binaries-up-to-date.js
diff --git a/test/mjsunit/wasm/ensure-wasm-binaries-up-to-date.js b/test/mjsunit/wasm/ensure-wasm-binaries-up-to-date.js
new file mode 100644
index 0000000000000000000000000000000000000000..02336f7c947321589779db4efba66d49865debd2
--- /dev/null
+++ b/test/mjsunit/wasm/ensure-wasm-binaries-up-to-date.js
@@ -0,0 +1,18 @@
+// Copyright 2016 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
+
+// Ensure checked in wasm binaries used by integration tests from v8 hosts
+// (such as chromium) are up to date.
+
+load('test/mjsunit/mjsunit.js');

[bradnelson, 2016/08/18 03:14:45]

This doesn't blow up?

[Mircea Trofin, 2016/08/18 03:15:55]

Where would it blow up? This is only run on the v8 side. The chrome side is
interested in the wasm
file.

+
+(function ensure_incrementer() {
+  var buff = readbuffer("test/mjsunit/wasm/incrementer.wasm");
+  var mod = new WebAssembly.Module(buff);
+  var inst = new WebAssembly.Instance(mod);
+  var inc = inst.exports.increment;
+  assertEquals(3, inc(2));
+}())