#5080 fixes part of the problem for me, but I’m still able to reproduce the same wasm-bindgen CLI failure on a wasm module.

What I’m seeing:

• The module contains many additional globals such as GOT.func.internal.*
• It also has a global named __stack_pointer
• But __stack_pointer is not exported

When wasm-bindgen runs on that module, it still panics during descriptor interpretation with:

called Result::unwrap() on an Err value: failed to find 32752 in function table

A local workaround is to force-export __stack_pointer from the wasm module. Once I do that, the same wasm-bindgen revision succeeds without any further changes.

So the remaining gap seems to be:

• wasm-bindgen-cli-support interpreter assumes every global.get/global.set is __stack_pointer #5080 handles the case where __stack_pointer is exported
• but if the module only has a named __stack_pointer global and does not export it, the interpreter still falls back to the old “all globals are stack pointer” behavior

Hope this helps.