Ben Smith
Ben Smith
Thanks for pointing out, this seems like an oversight. The wasm-c-api is implemented (the C part anyway, not C++ yet), but it seems that shared library isn't included in the...
This is an "error" because the custom `dynlink` section is malformed. `wasm-validate` currently fails in this case, but will just produce only a warning if run with `--ignore-custom-section-errors`. Perhaps this...
Thanks for reporting! I'll take a look.
Sorry I didn't respond to this, I was away on leave for the past 5 months! It seems like this shouldn't be too difficult to do. By the time the...
This is a good point. Currently the wabt IR doesn't distinguish between element expressions and element indexes internally, so it can't know what the original encoding was. But you're right,...
Looks like it is trying to read the `dylink` custom section, and erroring out because it's missing that field. @sbc100 looks like you added this, do you know what may...
There are some examples from the wasm-c-api that are used as basic tests (see https://github.com/WebAssembly/wabt/blob/master/CMakeLists.txt#L570), but I agree, there could be more here.
The C API is implemented, but the C++ API still needs to be done.
I think I saw a similar bug to this before, and it was due to a bug in wasm2js that was fixed in emsdk-latest. In fact, I recently updated libwabt.js...