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

extensions/amd: Add VK_AMD_anti_lag extension #943

Merged
merged 1 commit into from
Dec 2, 2024
Merged

Conversation

MarijnS95
Copy link
Collaborator

@MarijnS95 MarijnS95 commented Sep 19, 2024

No description provided.

@MarijnS95 MarijnS95 mentioned this pull request Sep 19, 2024
55 tasks
Comment on lines +6 to +10
/// <https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/vkAntiLagUpdateAMD.html>
#[inline]
#[doc(alias = "vkAntiLagUpdateAMD")]
pub unsafe fn anti_lag_update(&self, data: &vk::AntiLagDataAMD<'_>) {
(self.fp.anti_lag_update_amd)(self.handle, data)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://registry.khronos.org/vulkan/specs/latest/man/html/vkAntiLagUpdateAMD.html docs are a bit vague, they say:

If pData is not NULL...

Yet the respective VUID-vkAntiLagUpdateAMD-pData-parameter lacks the if `pData` is not `NULL`, `pData` must be a valid pointer to a valid... comment, as if it is not valid to leave this pointer NULL to begin with.

I'll leave it like this without Option and perhaps request a small spec update to remove the misleading is not NULL comment. CC @oddhack.

@MarijnS95 MarijnS95 merged commit 0b5b1a4 into master Dec 2, 2024
20 checks passed
@MarijnS95 MarijnS95 deleted the amd-anti-lag branch December 2, 2024 12:02
@MarijnS95 MarijnS95 added this to the Ash 0.39 with Vulkan 1.4 milestone Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants