Ben L. Titzer

I've started collection projects for students who would like to work with me. Several are Wasm-related. https://github.com/titzer/student-projects/

What about an `branch-hint` instruction that indicates the hint for the next following branch-like bytecode? It would be a no-op; i.e. it would have no effect on execution. That way...

FWIW I have a solution to making existing wasm bytecode efficiently interpretable (in-place, without modifying the bytes), which I have implemented in https://github.com/titzer/wizard-engine. The solution is to use a side-table...

Re: stack-walking API, I think it is far simpler, in terms of total system complexity, for applications to just use a shadow stack in memory. Wasm engines do not currently...

Based on the memory management in V8 for array buffers, especially shared buffers, it would be quite difficult to support `memory.shrink`, so I mostly concur with @lukewagner here.

I think the best that can be hoped for would be somewhat vague. First, I believe confounding factors like register allocation and calling conventions will make predicting performance very hard....

I think `pick` and `dup` would be very useful for many producers. As for type refinement, the `br_on_cast` instruction from the GC proposal does flow-sensitive type refinement, as does `br_on_null`,...

Thanks for your questions and concerns. It's worth noting that many of the designers and implementors of WebAssembly have backgrounds in high performance, industrial JITs, not only for JavaScript (V8,...

There is no single-pass verification algorithm for irreducible control flow that I am aware of. The design choice for reducible control flow only was highly influenced by this requirement. As...

I can also say further that if irreducible constructs were to be added to WebAssembly, they would not work in TurboFan (V8's optimizing JIT), so such functions would either end...