6ac2579f23
The result of an f64 binop was marked as f32 on Liftoffs value stack. This lead to errors and is fixed in this CL. I plan to clean up all binop implementions in a follow-up CL. R=titzer@chromium.org Bug: chromium:812005, v8:6600 Change-Id: I5bcd5c2e7d2b6170ef60f5e83cf2876b3475c38a Reviewed-on: https://chromium-review.googlesource.com/924025 Reviewed-by: Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#51375}
17 lines
571 B
JavaScript
17 lines
571 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.
|
|
|
|
load('test/mjsunit/wasm/wasm-constants.js');
|
|
load('test/mjsunit/wasm/wasm-module-builder.js');
|
|
|
|
const builder = new WasmModuleBuilder();
|
|
builder.addFunction(undefined, kSig_d_v).addBody([
|
|
...wasmF64Const(0), // f64.const 0
|
|
...wasmF64Const(0), // f64.const 0
|
|
...wasmI32Const(0), // i32.const 0
|
|
kExprBrIf, 0x00, // br_if depth=0
|
|
kExprF64Add // f64.add
|
|
]);
|
|
builder.instantiate();
|