Stream: wasmtime

Topic: Got out of bounds memory access from memory.atomic.notify

view this post on Zulip 12101111 (Sep 22 2022 at 13:55):

I run the following wat in wasmtime and got "wasm trap: out of bounds memory access".

(module
  (type (;0;) (func))
  (func (;0;) (type 0)
    (local i32)
    i32.const 1024
    i32.const 1
    memory.atomic.notify
    drop)
  (memory (;0;) 1 1 shared)
  (export "memory" (memory 0))
  (export "_start" (func 0)))

Does anyone know where the problem is ?

The code is trim down from lld's __wasm_init_memory

view this post on Zulip Alex Crichton (Sep 22 2022 at 14:08):

This is probably a bug in the memory.atomic.notify instruction implementation, which wasmtime does not fully support

Last updated: Nov 22 2024 at 17:03 UTC