Yuri Iozzelli

I remember that a problem with code section offsets was that there may be multiple code sec]tions in the future. How do DWARF and relocations handle that?

About the custom section vs instruction issue regarding tools: Let's say that we add branch hinting as new instructions. These instructions are semantically a NOP, but we require nonetheless all...

I am trying to summarize the discussion into a concrete plan for updating the branch hinting proposal. I agree with the general idea of [this comment](https://github.com/WebAssembly/design/issues/1424#issuecomment-884494675) , but also with...

@unicomp21 indeed we (Leaning Technologies) are interested in tail calls for [CheerpX](https://leaningtech.com/cheerpx/). We use them to implement X86 indirect jumps. The alternative is a trampoline-like solution, but it is quite...

@lars-t-hansen Good to know! We haven't seriously looked into doing this yet, but if/when we do we will get in touch for sure.

Ah right, I didn't run the tests. I applied your patch (thanks!) and they pass now

[webvm.io](https://webvm.io) developer here, offering some context: We managed to make headscale work with the wasm client in this fork: https://github.com/leaningtech/headscale We always meant to try to upstream the changes, but...

It is supported when using the official Tailscale control plane. A web client requests a regular websocket connection instead of upgrading the http connection to "tailscale-control-protocol". You can see the...

@calvinweb please report this problem (with more details) in your existing open issue in the webvm repo: https://github.com/leaningtech/webvm/issues/93 The headscale fork does work, we have users actively using it. So...

@rossberg I tried a different approach, with the goal of minimizing the changes to the main interpreter logic. As previously discussed, the main idea is to let the custom handlers...