Explicitly state that VkDeviceOrHostAddressConstKHR is also ignored #2205
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
dgkoch
approved these changes
Aug 31, 2023
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.
The spec only mentions that
vkGetAccelerationStructureBuildSizesKHRignoresVkDeviceOrHostAddressKHRvalues, but there are alsoVkDeviceOrHostAddressConstKHRvalues.VkAccelerationStructureGeometryTrianglesDataKHR::transformData, which is mentioned explicitly in the second half of the sentence as an exception, is aVkDeviceOrHostAddressConstKHRvalue. So I assume that both types are really meant to be ignored by this function. This PR clarifies that.