Wrong type when using wasm2wat or wasm-objdump to translate the Binaryen generated Wasm.

[Shawdox]

When I tried to use wasm2wat or wasm-objdump to translate the .wasm file (generated from ./scripts/fuzz_opt.py) to .wat format, I got the following errs:

1. Using wasm2wat:

wasm2wat 1.wasm -o 1.wat # 000000e: error: unexpected type form (got 0x5f)

2. Using wasm-objdump:

wasm-objdump -d 1.wasm # 5.wasm: file format wasm 0x1 # 0000017: error: expected valid param type (got -0x1d) # 000063d: error: invalid section code: 14 # 000079e: error: invalid global type: 0xffffffe4 # 00015a2: error: expected valid local type # ...

Since the Wasm generated by Binaryen is valid and free from undefined behaviors, I am a little bit puzzled why this happened. I've attached the target wasm file and did I get something wrong or it is normal?
Wasm file: 1.zip

[tlively]

wasm2wat and wasm-objdump do not know about WasmGC type definitions. I would recommend using wasm-tools (https://github.com/bytecodealliance/wasm-tools) to do your wasm-to-wat conversions instead.

[Shawdox]

Thanks! I also find discussions about this:

• The wat2wasm tool already supports wasmGC, such as struct.new  wabt#2363
• Plan for GC and beyond wabt#2348