Skip to content
New issue

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

Document resource binding annotations in language spec #55

Open
Tracked by #23 ...
damyanp opened this issue Sep 3, 2024 · 0 comments · May be fixed by microsoft/hlsl-specs#344
Open
Tracked by #23 ...

Document resource binding annotations in language spec #55

damyanp opened this issue Sep 3, 2024 · 0 comments · May be fixed by microsoft/hlsl-specs#344
Assignees

Comments

@damyanp
Copy link
Collaborator

damyanp commented Sep 3, 2024

We need to add resource binding annotations to the HLSL language spec. That includes the grammar, definition of register kinds, rules for which registers can bind to which resource types, and implicit binding rules.

@damyanp damyanp converted this from a draft issue Sep 3, 2024
@hekota hekota changed the title [HLSL] Document resource binding annotations in language spec Document resource binding annotations in language spec Sep 10, 2024
@damyanp damyanp assigned pow2clk and unassigned hekota Sep 23, 2024
@damyanp damyanp moved this to Active in HLSL Support Oct 7, 2024
pow2clk added a commit to pow2clk/hlsl-specs that referenced this issue Oct 22, 2024
This adds a resource chapter that documents typed and raw buffers including their methods and compatible operators along with short descriptions of their functionality. It also adds a description of binding annotations for all types. Stub sections are included for constant buffers and samplers, but no information is provided as yet.

Fixes llvm/wg-hlsl#55
Fixes llvm/wg-hlsl#56
@damyanp damyanp moved this from Active to Needs Review in HLSL Support Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs Review
Development

Successfully merging a pull request may close this issue.

3 participants