Skip to content
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

Missing image layout VUs #7688

Open
14 tasks
spencer-lunarg opened this issue Mar 14, 2024 · 2 comments
Open
14 tasks

Missing image layout VUs #7688

spencer-lunarg opened this issue Mar 14, 2024 · 2 comments
Assignees
Labels
Incomplete Missing Validation VUs to be added

Comments

@spencer-lunarg
Copy link
Contributor

spencer-lunarg commented Mar 14, 2024

these were added in 1.3.280 headers/spec (https://gitlab.khronos.org/vulkan/vulkan/-/merge_requests/6512)

  • VUID-vkCmdDraw-None-09600
  • VUID-vkCmdBeginRendering-pRenderingInfo-09588
  • VUID-vkCmdBeginRendering-pRenderingInfo-09589
  • VUID-vkCmdBeginRendering-pRenderingInfo-09590
  • VUID-vkCmdBeginRendering-pRenderingInfo-09591
  • VUID-vkCmdBeginRendering-pRenderingInfo-09592
  • VUID-vkCmdBeginRendering-pRenderingInfo-09593

other related Layout VUs

  • VUID-VkRenderPassCreateInfo-pAttachments-00836
  • VUID-vkCmdDraw-imageView-06172
  • VUID-vkCmdDraw-imageView-06173
  • VUID-vkCmdDraw-imageView-06174
  • VUID-vkCmdDraw-imageView-06175
  • VUID-vkCmdDraw-imageView-06176
  • VUID-vkCmdDraw-imageView-06177
@spencer-lunarg spencer-lunarg added the Incomplete Missing Validation VUs to be added label Mar 14, 2024
@danginsburg
Copy link

For what it's worth, I was just debugging corruption on AMD with VK_EXT_extended_dynamic_state where I was setting vkCmdSetDepthWriteEnableEXT to true with a depth/stencil buffer in VK_IMAGE_LAYOUT_DEPTH_READ_ONLY_STENCIL_ATTACHMENT_OPTIMAL. As far as I can tell, it would have been one of the 06174 VUIDs that should have caught this. I was going to file a bug that it was missing, but I guess it's already being tracked here. I'm also curious if validation was planning to check if the PSO/dynamic state had depth writes on because it's not entirely clear to me if that VU would have covered it since it doesn't explicitly mention that state.

@spencer-lunarg
Copy link
Contributor Author

I'm also curious if validation was planning to check if the PSO/dynamic state had depth writes

so the thing that stopped me before from "just quickly adding this" was the part of the VU where it says

this command must not write any values to the depth attachment

So this has a lot of things that could stop the writing like depthWriteEnable (which is also gated on depthTestEnable)

from my handy depth graph I assume after the depthWriteEnable (which we track if from static or dynamic) we should consider it as "written"

(Knowing this is a real VU that would have helpped someone, can put this up on my todo list for the upcoming weeks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Incomplete Missing Validation VUs to be added
Projects
None yet
Development

No branches or pull requests

2 participants