4 ms·
What's the strategy with dealing with 32-bit vs 64-bit machines? Historic attempts at using LLVM IR as a universal binary have stumbled on that issue, and typi
by willvarfar 8y ago
What's the strategy with dealing with 32-bit vs 64-bit machines?
Historic attempts at using LLVM IR as a universal binary have stumbled on that issue, and typically have ended up deciding to support the lowest-common-denominator machines i.e. 32-bit, meaning that it hasn't been viable to use them for server-style software.
- maxmcd 8y agoWasm is split between wasm32 and wasm64 they are separate https://github.com/WebAssembly/design/blob/master/FutureFeatures.md#linear-memory-bigger-than-4-gib https://github.com/WebAssembly/design/blob/master/FutureFeat... So yes, we're at the lowest common denominator for addressing memory. You would need to explicitly build for wasm64 in the future. Within wasmer wasm is compiled into a different IR through cranelift. That generally compiles for 64 bit systems but can compile to 32: https://github.com/CraneStation/wasmtime/pull/44 https://github.com/CraneStation/wasmtime/pull/44 Not sure if this entirely answers your question. Seems like there are still a handful for decisions wasmer would need to make in terms of what exactly is supported.