-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[HLSL] Implement implicit resource binding #110722
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
Labels
HLSL
HLSL Language Support
Comments
This was referenced Oct 1, 2024
53 tasks
We need to find an owner for this who can drive taking it to a design meeting to get this task ready to be worked on. |
bogner
added a commit
to bogner/llvm-project
that referenced
this issue
Apr 16, 2025
Implicit bindings will cause very confusing crashes in the backend at present, so this is intended at least partially as a stop gap until we get them implemented (see llvm#110722). However, I do think that this is useful in the longer term as well as an off-by-default warning, as it is quite easy to miss a binding or two when using explicit bindings and the results of that can be surprisingly hard to debug. I've filed llvm#135907 to track turning this into an off-by-default warning or removing it eventually as we see fit.
This was referenced Apr 16, 2025
bogner
added a commit
that referenced
this issue
Apr 16, 2025
Implicit bindings will cause very confusing crashes in the backend at present, so this is intended at least partially as a stop gap until we get them implemented (see #110722). However, I do think that this is useful in the longer term as well as an off-by-default warning, as it is quite easy to miss a binding or two when using explicit bindings and the results of that can be surprisingly hard to debug. I've filed #135907 to track turning this into an off-by-default warning or removing it eventually as we see fit.
var-const
pushed a commit
to ldionne/llvm-project
that referenced
this issue
Apr 17, 2025
Implicit bindings will cause very confusing crashes in the backend at present, so this is intended at least partially as a stop gap until we get them implemented (see llvm#110722). However, I do think that this is useful in the longer term as well as an off-by-default warning, as it is quite easy to miss a binding or two when using explicit bindings and the results of that can be surprisingly hard to debug. I've filed llvm#135907 to track turning this into an off-by-default warning or removing it eventually as we see fit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Implement implicit binding design as specified in llvm/wg-hlsl#177.
The implicit bindings part of the bindings approach was originally described in #58051, and is a follow up to #110719.
The text was updated successfully, but these errors were encountered: