We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://github.com/WebAssembly/branch-hinting/blob/main/proposals/branch-hinting/Overview.md
A new section in Wasm modules containing likelihood hints for branch instructions, allowing engines to generate more optimal code.
To be in line with other Wasm features, I expect that the name will be wasm-branch-hinting.yml. The group is "webassembly".
wasm-branch-hinting.yml
"webassembly"
According to the table at https://webassembly.org/features:
Chrome: requires flag Firefox: enabled in Nightly, requires flag in Beta/Stable Safari: enabled since 16
Chrome will enable it by default soon (likely in version 136 or 137): https://issues.chromium.org/issues/373151164
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Specification
https://github.com/WebAssembly/branch-hinting/blob/main/proposals/branch-hinting/Overview.md
Description
A new section in Wasm modules containing likelihood hints for branch instructions, allowing engines to generate more optimal code.
To be in line with other Wasm features, I expect that the name will be
wasm-branch-hinting.yml
. The group is"webassembly"
.Documentation
https://github.com/WebAssembly/branch-hinting/blob/main/proposals/branch-hinting/Overview.md
Browser support
According to the table at https://webassembly.org/features:
Chrome: requires flag
Firefox: enabled in Nightly, requires flag in Beta/Stable
Safari: enabled since 16
Chrome will enable it by default soon (likely in version 136 or 137): https://issues.chromium.org/issues/373151164
The text was updated successfully, but these errors were encountered: