Thanks for the feedback! I've updated the status accordingly, setting the feedback from Mozilla and web developers to Positive (after all it was championed by a web developer). I'm not sure if Mozilla already shipped the feature, but at least it's fully implemented since M127 <https://bugzilla.mozilla.org/show_bug.cgi?id=1837683>. I also set Apple's position to neutral since while we are not sure about their implementation plans, they were present at the phase 4 vote, actively participated in the discussion <https://github.com/WebAssembly/meetings/blob/main/main/2024/CG-06.md#branch-hinting-yuri-iozzelli> and did not oppose.
On Tue, Mar 25, 2025 at 2:01 PM Stephen Chenney <schen...@chromium.org> wrote: > I think you have a stronger interop story than the fields would > indicate ... > > On Tue, Mar 25, 2025 at 8:49 AM Emanuel Ziegler <ecmzieg...@chromium.org> > wrote: > >> Hi all, >> >> We are preparing to ship the WebAssembly Branch Hints proposal in M136 >> which has been voted to phase 4 in the Wasm Community Group last July. >> Chrome is now catching up with shipping it after requests from partners. >> The feature is already implemented in Firefox. >> >> The proposal was championed by Yuri Iozzelli from Leaning Technologies >> and the V8 team was not involved in its standardization process. The >> implementation has no effect on existing code by design which is why a >> Finch trial would not yield any insights. We have a Chromium feature >> available for a Finch kill-switch if necessary. >> >> Thank you, >> Emanuel >> >> >> Contact emailsecmzieg...@chromium.org, jkumme...@chromium.org >> >> ExplainerNone >> >> Specification >> https://github.com/WebAssembly/branch-hinting/blob/main/proposals/branch-hinting/Overview.md >> >> Summary >> >> Improves the performance of compiled WebAssembly code by informing the >> engine that a particular branch instruction is very likely to take a >> specific path. This allows the engine to make better decisions for code >> layout (improving instruction cache hits) and register allocation. >> https://github.com/WebAssembly/branch-hinting/blob/main/proposals/branch-hinting/Overview.md >> >> >> Blink componentBlink>JavaScript>WebAssembly >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EJavaScript%3EWebAssembly%22> >> >> TAG reviewNone >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> None >> >> >> *Gecko*: No signal >> > > In the summary it says that Firefox has shipped. Should the Gecko signal > be "Shipped"? > > >> >> *WebKit*: No signal >> >> *Web developers*: No signals >> > > And here you indicated that a developer pushed the proposal. Is that not a > signal of some kind? > > >> >> *Other signals*: >> >> WebView application risks >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> None >> >> >> Debuggability >> >> None >> >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?No >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ?No >> >> Flag name on about://flagsNone >> >> Finch feature nameV8Flag_experimental_wasm_branch_hinting >> >> Requires code in //chrome?False >> >> Estimated milestones >> Shipping on desktop 136 >> Shipping on Android 136 >> Shipping on WebView 136 >> >> Anticipated spec changes >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> None >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5165273114738688?gate=5186994509185024 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/>. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to blink-dev+unsubscr...@chromium.org. >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPAU7RwMXE%2BnsewWqSQ0M%2BS7gH600KjJtnp2T3Oyw8GPz4nNHg%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPAU7RwMXE%2BnsewWqSQ0M%2BS7gH600KjJtnp2T3Oyw8GPz4nNHg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPAU7RwevW%3D8PfZLobRo8wmBOBpuVkymGe4rqwhwAP6%3Dc2QOeQ%40mail.gmail.com.
