Update INF-0004-validator-hashing.md with applicable AgilitySDK version #373
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
Now that we know which AgilitySDK version will support hash bypass, the "TBD" in the spec can be replaced with the actual version. Also consider whether to move this out of "proposal" state, perhaps as soon as that AgilitySDK becomes available?
amarpMSFT
requested review from
llvm-beanz and
damyanp
and removed request for
llvm-beanz
damyanp
approved these changes
Jan 28, 2025
llvm-beanz
approved these changes
Feb 4, 2025
llvm-beanz
pushed a commit
to llvm-beanz/hlsl-specs
that referenced
this pull request
Feb 9, 2025
…on (microsoft#373) Now that we know which AgilitySDK version will support hash bypass, the "TBD" in the spec can be replaced with the actual version. Also consider whether to move this out of "proposal" state, perhaps as soon as that AgilitySDK becomes available?
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.
Now that we know which AgilitySDK version will support hash bypass, the "TBD" in the spec can be replaced with the actual version.
Also consider whether to move this out of "proposal" state, perhaps as soon as that AgilitySDK becomes available? Actually might need to stay in proposal state until any DXC side changes are finished, such as publishing dxil.dll?