Stream: wasmtime

Topic: Possible determinism issues

Olexiy Kulchitskiy (Apr 27 2022 at 16:09):

Hi, guys! I'm new to all this WASM stuff and looking for deterministic WASM runtime (for some POC). Please advise whether Wasmtime is handling non-determinism issues and if yes, how (would be nice to point to some article/code)?

Chris Fallin (Apr 27 2022 at 17:31):

Hi @Olexiy Kulchitskiy -- the execution of Wasm in Wasmtime should be completely deterministic with a few exceptions:

• if NaN canonicalization is not turned on (set it with this API on Config), then different hardware platforms may produce different bit patterns in the payload bits of NaNs
• imported functions should of course be deterministic; that's outside of Wasmtime's control
• If we eventually implement multithreading, then that would be a source of nondeterminism as well, but we currently do not
• I think that's it (others correct me if I missed anything?)

Chris Fallin (Apr 27 2022 at 17:32):

Ah, stack depth as well; the point at which one gets a stack-overflow trap is implementation-defined (but that should not be observable in any normally-returning Wasm call, as the trap terminates the instance)

bjorn3 (Apr 27 2022 at 17:56):

And the memory allocation limit.

Dan Gohman (Apr 27 2022 at 18:03):

You may also want to use the static_memory_forced API, to prevent memory.grow allocation from failing nondeterministically.

Olexiy Kulchitskiy (Apr 27 2022 at 18:57):

got it. Thank you

Lars Hansen (May 02 2022 at 08:44):

Relaxed SIMD will be deterministic per-platform but will appear nondeterministic across platforms - basically the same problem as for NaNs, but will require a different solution.

Last updated: Nov 22 2024 at 16:03 UTC