Fix arithmetic NaN handling in f32.nearest and f64.nearest

This commit is contained in:
Lachlan Sneff
2019-01-10 12:20:23 -05:00
parent c44dcfec2b
commit 2e26f8547e
4 changed files with 93 additions and 126 deletions

View File

@ -11,51 +11,8 @@ fn main() {
fn create_module_1() -> Box<Instance> {
let module_str = "(module
(type (;0;) (func))
(type (;1;) (func))
(type (;2;) (func (param i64 i64 f64 i64 f64 i64 f32 i32)))
(type (;3;) (func (param f64 i64 f64 i64 f64 i64 f32 i32)))
(func (;0;) (type 0))
(func (;1;) (type 3) (param f64 i64 f64 i64 f64 i64 f32 i32))
(func (;2;) (type 0))
(func (;3;) (type 3) (param f64 i64 f64 i64 f64 i64 f32 i32))
(func (;4;) (type 3) (param f64 i64 f64 i64 f64 i64 f32 i32))
(func (;5;) (type 2) (param i64 i64 f64 i64 f64 i64 f32 i32))
(func (;6;) (type 2) (param i64 i64 f64 i64 f64 i64 f32 i32))
(func (;7;) (type 0)
f64.const 0x0p+0 (;=0;)
i64.const 0
f64.const 0x0p+0 (;=0;)
i64.const 0
f64.const 0x0p+0 (;=0;)
i64.const 0
f32.const 0x0p+0 (;=0;)
i32.const 0
i32.const 0
call_indirect (type 3)
f64.const 0x0p+0 (;=0;)
i64.const 0
f64.const 0x0p+0 (;=0;)
i64.const 0
f64.const 0x0p+0 (;=0;)
i64.const 0
f32.const 0x0p+0 (;=0;)
i32.const 0
i32.const 2
call_indirect (type 3)
f64.const 0x0p+0 (;=0;)
i64.const 0
f64.const 0x0p+0 (;=0;)
i64.const 0
f64.const 0x0p+0 (;=0;)
i64.const 0
f32.const 0x0p+0 (;=0;)
i32.const 0
i32.const 3
call_indirect (type 3))
(table (;0;) 7 7 anyfunc)
(export \"signature-implicit-reused\" (func 7))
(elem (;0;) (i32.const 0) 4 2 1 4 0 5 6))
(import \"spectest\" \"memory\" (memory (;0;) 0))
(data (;0;) (i32.const 0) \"\"))
";
let wasm_binary = wat2wasm(module_str.as_bytes()).expect("WAST not valid or malformed");
let module = wasmer_runtime::compile(&wasm_binary[..], &CraneliftCompiler::new()).expect("WASM can't be compiled");