3.1.15 released - new implementation of metadata extraction

[Sam Clegg]

3.1.15 was released last week and it is the first release to use direct metadata extraction in emscripten rather than relying on wasm-emscripten-finalize to dump information about the linked wasm binary.

We don't know of any issues, but if you do experience any problems that you suspect could be related to this change you can temporarily revert to the old method by setting EMCC_READ_METADATA=binaryen in the environment. 

cheers,

sam

[Floh]

Is this in any way related to the EM_JS() magic? 

In any case, I'm using EM_JS() quite a lot in my code and everything still appears to working after updating to 3.1.15.

Cheers!

-Floh

[Sam Clegg]

On Fri, Jul 8, 2022 at 8:43 AM Floh <flo...@gmail.com> wrote:

Is this in any way related to the EM_JS() magic? 

Yes, we need to extract EM_JS strings from the wasm module, but also lots of other things such as the list of imports & exports.

In any case, I'm using EM_JS() quite a lot in my code and everything still appears to working after updating to 3.1.15.

Sweet!

 

Cheers!

-Floh

On Tuesday, 5 July 2022 at 18:28:12 UTC+2 s...@google.com wrote:

3.1.15 was released last week and it is the first release to use direct metadata extraction in emscripten rather than relying on wasm-emscripten-finalize to dump information about the linked wasm binary.

We don't know of any issues, but if you do experience any problems that you suspect could be related to this change you can temporarily revert to the old method by setting EMCC_READ_METADATA=binaryen in the environment. 

cheers,

sam

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/76cb5377-01fb-4b86-8956-ddee7b85be7fn%40googlegroups.com.