-
Notifications
You must be signed in to change notification settings - Fork 415
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
layers: Cleanup vkCmdBeginRendering #9138
layers: Cleanup vkCmdBeginRendering #9138
Conversation
CI Vulkan-ValidationLayers build queued with queue ID 337789. |
de90be0
to
d1674d0
Compare
CI Vulkan-ValidationLayers build queued with queue ID 337804. |
CI Vulkan-ValidationLayers build # 18527 running. |
CI Vulkan-ValidationLayers build # 18527 passed. |
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.
There is a mixture of plain continue;
and ASSERT_AND_CONTINUE
, everything ok? Easy to conflate them
the goal was to clarify it... it is valid to have going if (color_attachment.imageView == VK_NULL_HANDLE) continue;
auto image_view_state = Get<vvl::ImageView>(color_attachment.imageView);
ASSERT_AND_CONTINUE(image_view_state); should make it clear if things are null, skip, else we can rely the |
CI Vulkan-ValidationLayers build queued with queue ID 338400. |
CI Vulkan-ValidationLayers build # 18541 running. |
d1674d0
to
40bd589
Compare
CI Vulkan-ValidationLayers build queued with queue ID 338471. |
CI Vulkan-ValidationLayers build # 18544 running. |
40bd589
to
9a21fe1
Compare
CI Vulkan-ValidationLayers build queued with queue ID 338502. |
CI Vulkan-ValidationLayers build # 18546 running. |
CI Vulkan-ValidationLayers build # 18546 passed. |
The logic for
vkCmdBeginRendering
was all over the place between Stateless, CoreCheck, and Best PracticeTried to unify things (naming, how things are broken up, etc) and group things as there is a lot going on and hard to follow it at first read