SingleAccretion

WASM files with a Tags section are not supported

1

WASM files with a tag section (i. e. those produced by compilers targeting the EH proposal) fail to parse: ``` > twiggy top HelloWasm.wasm error: WASM error: Invalid section code...

Missing support for the (somewhat) recently added relocation types

2

See https://github.com/llvm/llvm-project/blob/e56ad22b4a41e65984d6997b2c2496a20f906d1d/llvm/include/llvm/BinaryFormat/WasmRelocs.def#L27-L31 and https://github.com/WebAssembly/wabt/blob/1edeaf2948b4afd711e50ba2007ee44503cd80fe/src/common.cc#L46-L59 I hit it specifically with `R_WASM_FUNCTION_INDEX_I32`. This affects e. g. `wasm-objdump -x -j linking`.

C#: the generated finalization logic does not take child resources into account

10

Currently, the generated resource types have a finalizer, like [this](https://github.com/dotnet/runtime/blob/7ff684af49cdf008bebbe10efcc10a2649795d65/src/libraries/System.Net.Http/src/System/Net/Http/WasiHttpHandler/WasiHttpWorld.wit.imports.wasi.http.v0_2_1.ITypes.cs#L5279-L5281). This logic is not correct if the resource type may have child resources - this will trap on `drop`. See...

Reproduction: ``` > wasmtime compile -D debug-info -O opt-level=0 wasm-with-di.wasm > llvm-objdump wasm-with-di.cwasm ``` Expected result: the output does not contain an excessive number of relocations. Actual result: there are...

See #9470 and the corresponding `TODO-Bug?` in source.