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

Vulkan: Support of VK_KHR_maintenance2 extension #2503

Merged
merged 1 commit into from
Dec 27, 2018

Conversation

Qining
Copy link
Contributor

@Qining Qining commented Dec 27, 2018

Note the dependency change introduced by
VkInputAttachmentAspectRefernceKHR is not handled yet.

Following Note and TODO added as comments

The intput attachment aspect info is only cached but not used for now, so the
dependency can be wrong as a draw call may depends on just one aspect of a
depth stencil image, as specified in the input attachment aspect info, while
GAPID will still treat both aspects as dependees.

TODO: Once the CL that enables us getting used descriptors from shader is in,
we can pull input_attachment_index from the information of the used
descriptors then use the input attachment aspect info to fix the dependency.

Note the dependency change introduced by
`VkInputAttachmentAspectRefernceKHR` is not handled yet.

Following Note and TODO added as comments

The intput attachment aspect info is only cached but not used for now, so the
dependency can be wrong as a draw call may depends on just one aspect of a
depth stencil image, as specified in the input attachment aspect info, while
GAPID will still treat both aspects as dependees.

TODO: Once the CL that enables us getting used descriptors from shader is in,
we can pull `input_attachment_index` from the information of the used
descriptors then use the input attachment aspect info to fix the dependency.
@Qining Qining merged commit 9827ce7 into google:master Dec 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants