The wasm file does not have GC, but does have exceptions - I am guessing that is relevant somehow. First, the wasm is valid with the right features:
$ bin/wasm-opt a.wasm --all-features --disable-fp16 --disable-simd --disable-bulk-memory --disable-gc --disable-strings --disable-stack-switching --disable-custom-descriptors --disable-memory64 --disable-strings --disable-multimemory --disable-shared-everything --disable-bulk-memory-opt --disable-relaxed-atomics --print > a.wat
That also prints out the wat text. But that wat is not valid with the same features:
$ bin/wasm-opt a.wat --all-features --disable-fp16 --disable-simd --disable-bulk-memory --disable-gc --disable-strings --disable-stack-switching --disable-custom-descriptors --disable-memory64 --disable-strings --disable-multimemory --disable-shared-everything --disable-bulk-memory-opt --disable-relaxed-atomics
Fatal: a.wat:73:1: error: invalid type: distinct rec groups would be identical after binary writing
But there are no rec groups (as there is no GC). Line 73 has
(type $71 (func (result f64 exnref i64 nullexternref)))
cc @tlively
a.wasm.gz
The wasm file does not have GC, but does have exceptions - I am guessing that is relevant somehow. First, the wasm is valid with the right features:
That also prints out the wat text. But that wat is not valid with the same features:
But there are no rec groups (as there is no GC). Line 73 has
cc @tlively
a.wasm.gz