Add information on packed_4x8_integer_dot_product extension #36898
+5
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chrisdavidmills
requested review from
wbamberg
and removed request for
a team
github-actions
bot
added
Content:WebAPI
2 tasks
|
Preview URLs External URLs (1)URL:
|
wbamberg
reviewed
Nov 21, 2024
| @@ -21,6 +21,11 @@ The `WGSLLanguageFeatures` object is accessed via the {{domxref("GPU.wgslLanguag | |||
| ## Available features | |||
|
|
|||
| The available WGSL language extensions can vary across implementations and physical devices and may also change over time; we have therefore not listed them here. For a complete list, refer to [WGSL language extensions](https://gpuweb.github.io/gpuweb/wgsl/#language-extension) in the WGSL specification. | |||
| The following WGSL language extensions are defined at [WGSL language extensions](https://gpuweb.github.io/gpuweb/wgsl/#language-extension) in the WGSL specification. Bear in mind that the exact set of features available will vary across implementations and physical devices, and may change over time. | |||
|
|
|||
| | Feature name | Description | | |||
There was a problem hiding this comment.
I'm not sure what the reasoning for this format is.
- It's much harder to edit or read the source than a Markdown
<dl>or just headings. - It means you have to embed HTML in the source to get paragraphs
- We have something that looks to users like a link, that doesn't go anywhere if you click it
- The
<a>element usesnamewhich is deprecated according to our docs. - You only get about 2/3 of the page width for the description text.
Why not use a Markdown <dl>, or just headings?
|
This pull request has merge conflicts that must be resolved before it can be merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Chrome 123 supports the
readonly_and_readwrite_storage_textureslanguage extension (seeWGSLLanguageFeatures), which allows:In your WGSL shader code.
This PR adds an entry to the "Available features" table on the
WGSLLanguageFeaturesref page for this feature. I'm copying the same structure as I used in #36880, and will deal with merging them as they start to get published.See https://developer.chrome.com/blog/new-in-webgpu-123#dp4a_built-in_functions_support_in_wgsl for the data source.
Motivation
Additional details
Related issues and pull requests
Project issue: #36349