Sam Clegg

If you want to link you wasm assmembly code into an emscripten project then the simplest way to do this would be write in using the LLVM assembly format and...

> Thanks [@sbc100](https://github.com/sbc100). Actually the code is written in WAST already which is much easier to code. I don't think writing llvm asm is an option here. > Are you...

> I thought that the dynamic linking was against the wasm itself, not the intermediate object. I'm afraid I don't quite understand the question. Can you elaborate?

The more complex way that it sounds like you are proposing would be to somehow to try to dynamically link wasm module that was not build by emscripten with and...

`wat2wasm -r` is designed to be able to produce object files that can then be fed into the static linker. It does not produce emscripten dynamic libraries (side modules). (It...

> > wat2wasm -r is designed to be able to produce object files that can then be fed into the static linker. It does not produce emscripten dynamic libraries (side...

Can you share the object produced by `wat2wasm -r` (the one that should be defining `orc_add2_rshift_sub_s16_11_op`).. I can probably tell you what is wrong it it. As we go down...

In addition to being easily convertible to a valid object file, the LLVM assembly format also has some added advantages over wat such as support the C pre-processor and supporting...

So it looks like you ended up writing your own wasm object file writer? (Is that right? I don't see any .wat content in your PR) Very cool! I thought...

Does debugging work for you with a simple hello world program? (does it also work with dwarf split?)