-
Notifications
You must be signed in to change notification settings - Fork 14.9k
[DirectX] Make dx.RawBuffer an op that can't be replaced #154620
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
farzonl
merged 14 commits into
llvm:main
from
farzonl:bugfix/issue-152348_replaceOpWithVar_version
Aug 29, 2025
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
b51b68d
[DirectX] Make dx.RawBuffer an op that can't be replaced
farzonl c7d44ab
update to handle multiple phi nodes
farzonl 4853d0e
create new NoReplacement property
farzonl 90847c2
address PR comments
farzonl 2ead86b
address partial pr comments
farzonl e6af513
address more pr feedback
farzonl 533dc4f
make an is isTokenLikeTy() helper
farzonl 74a568f
fix isTokenLikeTy implementation
farzonl 65f6d7a
PR #155332 changed the handlefromimplicitbinding intrinsic signature.…
farzonl 93ff6d2
fix for hoisting non void returns
farzonl 5121bc1
pr comments
farzonl e4215bb
add verifer and simplifyCFG tests
farzonl b520011
remove undef
farzonl 1546848
fix test to comply with the new token like verifier changes
farzonl 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
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
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.
Do we need to do this on each iteration or would it be okay to remove all of the dead instructions at the end? I think we could probably get away with just one
DeadInsts
container and put both theCurrBB
andPrevBB
dead instructions in it together.Uh oh!
There was an error while loading. Please reload this page.
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 thought about that. The problem is the Intrinsic::dx_resource_getpointer needs to be replicated across the phi basic blocks before we do
Otherwise the Resources SmallVector will get populated with an intrinsic that is dead.
Similarly we can't remove the
br label %_Z6CSMainv.exit
until we are done iterating because those instructions are not in the current basic block we are evaluating. Thats forcing me to split the cleanup.I suppose what we could do is check if the II is in the DeadInsts vector and that could let us do cleanup once but was afraid a contains check might get expensive? Thoughts?
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.
If we need to check if the cleanup is already in the vector then consolidating the cleanup probably isn't really worth it. I'm fine with it being split as long as there's a good reason for it, but if it's straightforward to combine then that seems nicer.