arm64-specific: wasm fails to instantiate: out of bounds memory access

[davidmdm]

Describe the bug
Running a wasm binary returns the error:

error instantiating wasm binary: module[] function[_start] failed: wasm error: out of bounds memory access
wasm stack trace:
        .time.__dataIO_.big8(i32) i32
        .github.com_BurntSushi_toml_internal.init(i32) i32
        .runtime.doInit1(i32) i32
        .runtime.main(i32) i32
        .wasm_pc_f_loop()
        ._rt0_wasm_wasip1()

To Reproduce
Running on Darwin/arm64 M2 chip

set -x

if [ ! -d "yoke" ]; then
  git clone --depth=1 https://github.com/yokecd/yoke.git
fi

(
  cd yoke
  GOOS=wasip1 GOARCH=wasm go build -o ../redis-installer.wasm ./examples/redis
)

# will run successfully
go run github.com/tetratelabs/wazero/cmd/[email protected] run ./redis-installer.wasm

# will fail with aforementioned error
go run github.com/tetratelabs/wazero/cmd/[email protected] run ./redis-installer.wasm

Expected behavior
Expected same output as [email protected]

Environment (please complete the relevant information):

• Go version: 1.24.0
• wazero Version: 1.9.0
• Host architecture: arm64
• Runtime mode: compiler

[evacchi]

can you run this with amd64 emulation to see if it's specific to arm64? this should do it:

GOARCH=amd64 go run github.com/tetratelabs/wazero/cmd/[email protected] run ./redis-installer.wasm

[davidmdm]

@evacchi it works under amd64 emulation. So its a bug specific to arm64!

[davidmdm]

Perhaps still a trampoline issue? I remember when certain programs would hang in version 1.7.x and that a fix was made to the arm64 backend then. Perhaps an off-by-one of sorts is causing a memory out of bounds issue?

[evacchi]

@davidmdm out of curiosity, have you tried against Go 1.23? let's rule out something related to #2375

[davidmdm]

@evacchi Just ran against a version with the wasm produced by go1.23.6 and it produces an identical error.
I checked the new wasm did not match the one produced by go1.24.0 as well to be sure.

[ncruces]

I don't think that's what @evacchi asked for. Don't build the Wasm with 1.23, rather use 1.23 to go run wazero.

[davidmdm]

@ncruces Good catch. I got that confused.

@evacchi Same result unfortunately!

GOTOOLCHAIN=go1.23.6 go run github.com/tetratelabs/wazero/cmd/[email protected] run ./redis-installer.wasm

go: downloading go1.23.6 (darwin/arm64)
error instantiating wasm binary: module[] function[_start] failed: wasm error: out of bounds memory access
wasm stack trace:
        .time.__dataIO_.big8(i32) i32
        .github.com_BurntSushi_toml_internal.init(i32) i32
        .runtime.doInit1(i32) i32
        .runtime.main(i32) i32
        .wasm_pc_f_loop()
        ._rt0_wasm_wasip1()
exit status 1

[evacchi]

interesting, so unrelated issue