-
Notifications
You must be signed in to change notification settings - Fork 14k
[DirectX] Gather resource names in DXIL resource analysis #140633
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
8776c02
[HLSL] Add resource name argument to resource class constructors
hekota a0b6179
[DirectX] Add resource name argument to llvm.dx.handlefrombinding int…
hekota eacedc9
add test to make sure strings are removed; fix buffer-frombinding.ll …
hekota 61c8945
update DirectXTests
hekota a73cdb9
[DirectX] Gather resource names in resource analysis
hekota a756f4d
code review feedback - add assert, llvm__unreachable, and refactor to…
hekota d1861a4
Merge branch 'main' of https://github.com/llvm/llvm-project into reso…
hekota b6648e9
fix merge
hekota File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The best reason I can see to include this here and not as part of the ResourceBinding member is to make it more readily accessible to
getName
, but I don't see that as being called at all? The other use of the name is in #140982 where it could be simplified as being part of theBinding
compare instead of another parameter tostd::tie
. It works either way though.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that it is called for pretty print reasons, even so, the name could be retrieved from the binding member.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The name is also used for generating DXIL metadata related to resources (#140635) and for diagnostics. The
ResourceBinding
struct contains information related to the binding, I don't think the name should be included in the struct.