Andrew Brown
Andrew Brown
@brianjjones, I refactored the `tf.js` file in [this commit](https://github.com/abrown/wasmtime/commit/a9ddd19876a366c1509b80a623056bc0e2c0d952). This should address some of the comments I made above. There is more refactoring that could/should be done in that area...
> content authors don't have to configure and compile their own runtime I am in favor of @tschneidereit's point of making it really easy for users to test new WASI...
cc: @jlb6740
I have been looking around for a good way to use V8's Wasm features from Rust and this might fit the bill: is there a plan to release a finished...
(I guess the alternative would be to expose [WasmModuleObject](https://chromium.googlesource.com/v8/v8/+/refs/heads/master/include/v8.h#92) and related classes?)
Ah, good point; I didn't read #173 carefully enough. Let me edit out that part of the issue above.
For ARM in V8 it takes [1 instruction to lower `f32x4.convert_i32x4_u`](https://github.com/v8/v8/blob/19be4913881bb02c5d9b4f1c7547ee2d1273120b/src/compiler/backend/arm64/code-generator-arm64.cc#L1893).
cc: @rrwinterton, @arunetm
Cranelift's SSA form has types for each value; if you try to use an `I8` value somewhere as an `I64` then it will extend it appropriately. (That is my hazy...
But looking at the V8 implementation: why not XOR the tmp register as is done currently and use setcc?