Sam Clegg

Maybe you don't need data relocations in pascal? But this kind of relocation is currently not representable in wat format (at global scope): ``` int bar = 1; int foo...

> > But this kind of relocation is currently not representable in wat format (at global scope) > > No, they don't. The problem is that effective address of `bar`...

> on the topic of `call_indirect` relocation. > > per this document: https://github.com/WebAssembly/tool-conventions/blob/master/Linking.md#merging-function-sections > > > There are currently two ways in which function indices are stored in the code...

In short, the `wat` format as it stands today is not suitable as a general purpose assembly language. Its can't describe object files in the general case.

The issue we are discussing here mostly refers to linking with other object files. if you are not using a linker then writing pure WAT is a lot more reasonable....

> Doesn't this problem also exist for relocations though? How do offsets work when linking anyways? Are data segments with constant offsets relocated during linking or do they interfere with...

Yes there is no support threads in WASI and no thread API to speak of. There it generally very little support for WASI in emscripten-generated code. Only the most trivial...

wasi-sdk (which is basically clang + wasi-libc) is your best bet if you are targeting WASI: https://github.com/WebAssembly/wasi-sdk emscripten tries it best to output WASI-compatible stuff where it can.. but this...

Yes, basically. The WebAssembly threads proposal doesn't include any APIs for creating of joining threads, only the core concepts of shared memory and the operations on it. I think WASI...

This is really an llvm/clang issue, so perhaps better to file it there. The issue that we don't support "common" symbols currently (`Common symbols are not yet implemented for Wasm`)...