Yuri Iozzelli

I tried to implement branch hinting. You can see my attempt here: https://github.com/WebAssembly/branch-hinting/tree/annot_bh Decoding, parsing and checking are fine, but arranging and decoding aren't possible with the current custom handler...

The reason for putting the hint section before the code section is for making it easier for the consumer rather than the producer. I think that this is a common...

That's true, I hadn't considered that rearranging the sections prevents using real absolute offsets (at least without a second phase, but that would defeat the purpose of rearranging). At the...

I am trying to overcome the encoding and arranging issues for code metadata sections. For now I have a decent solution for the arranging issue (being able to emit annotations...

I finally managed to implement encoding for branch hinting (and any code metadata section). The full list of additions on top of the `unshare` branch can be seen here: https://github.com/WebAssembly/branch-hinting/pull/17...

@rossberg no worries. After yesterday's CG meeting though, I think that we need to change the design quite a bit. If we are going to remove `@custom`, we need to...

The no-op `branch-int` instruction seems like a good idea. I will add it to the presentation for Tuesday

I started drafting a repo for this proposal here: https://github.com/yuri91/branch-hinting There is a very brief [overview](https://github.com/yuri91/branch-hinting/blob/master/proposals/branch-hinting/Overview.md), and a folder with a minimal [benchmark](https://github.com/yuri91/branch-hinting/tree/master/benchmarks). The benchmark uses the `br_on_null` instruction, which...

I will try to summarize the discussion so far as I understand it, and address some of the issues: ### The problem There are a few proposals that concern the...

I agree with @kripken that having tools handle sections that they don't fully understand is not feasible. We are acting like there will be hundreds of such standardized sections, but...